Logical Inconclusive Reasoning — Evaluation Report

Dataset: data/toy_data.jsonl  ·  Generated: 2026-04-27  ·  Pipeline: agent_logic (haiku) + agent_NLI (haiku) → agent_eval (sonnet)

Sushma Anand Akoju

Contents

Overview

This report presents the results of a three-agent evaluation pipeline applied to a toy dataset of lexically ambiguous knowledge-base reasoning problems. Each record introduces a homonymous entity (e.g., bat, bank, wave) whose referent is deliberately underspecified, creating cases where standard entailment reasoning is insufficient and logical inconclusiveness must be detected and classified.

The pipeline comprises:

Aggregate Results

32
Total evaluated items
71.9%
MCQ accuracy (23/32)
56.3%
GOLD flag (18/32)
0
ERROR flags

Quality flag distribution

FlagCount%
GOLD1856.3%
REVIEW721.9%
CONFLICT721.9%
ERROR00.0%

Logic verdict distribution

VerdictCount%
Inconclusive2165.6%
True1031.3%
False13.1%
Paradox00.0%

NLI label distribution

LabelCount%
Neutral2268.8%
Entailment825.0%
Contradiction26.3%

Fallacy frequency

Fallacy typeOccurrences
Equivocation32
Hasty Generalization22
Affirming the Consequent16
Amphiboly5
False Premise2
Other0

Per-Key Results

bat — A homonymous entity spanning mammal and baseball equipment senses
Bat is a mammal. Bat is used in baseball. Bats have wings. Bats have a barrel. Wings are not barrels. Barrels are not wings. Bats can fly. There is a brown bat. Brown bat flew.
Inconclusive query
FieldValue
QueryBrown bat is a mammal.
Logic verdictInconclusive
NLI labelNeutral
Neutral classificationNeutral
Agents match✓
MCQ selected4. True if brown bat is a mammal and Inconclusive if brown bat could have been thrown by a baseball player.
MCQ correct✓
Quality flagGOLD
FallaciesEquivocation, Affirming the Consequent, Hasty Generalization
Both agents converge: agent_logic finds two possible worlds (World A: mammal→True; World B: baseball bat→False) with 'flew' compatible with both senses. agent_NLI labels Neutral via equivocation on 'bat'. The mutual-exclusion axioms (wings≠barrels) provide disambiguation only for the conclusive query, not here.
Flag rationale: Both agents fully agree on Inconclusive/Neutral with high confidence and the equivocation on 'bat' cleanly accounts for the inconclusiveness.
Conclusive query
FieldValue
QueryBrown bat has wings.
Logic verdictInconclusive
NLI labelEntailment
Neutral classificationNot Neutral
Agents match✗
MCQ selected1. True
MCQ correct✓
Quality flagREVIEW
FallaciesEquivocation, Hasty Generalization, Affirming the Consequent
Agents diverge: agent_logic returns Inconclusive (does not use 'wings' as a disambiguation signal). agent_NLI correctly applies the mutual-exclusion chain (wings≠barrels; baseball-bat has barrels; therefore 'has wings' entails mammal-sense) and returns Entailment/Not Neutral. The divergence reflects a systematic logic-agent limitation: it requires explicit predicate-to-sense resolution in the KB rather than inferring it from mutual-exclusion axioms.
Flag rationale: NLI correctly applies mutual-exclusion chain; logic agent fails to disambiguate via query predicate — one round of KB enrichment would resolve the divergence.
Neutral query
FieldValue
QueryIs 'Brown bat is a mammal' neutral or not neutral?
Logic verdictInconclusive
NLI labelNeutral
Agents match✓
MCQ correct✓
Quality flagGOLD
Both agents agree: the statement is Neutral/Inconclusive because 'brown bat' is referentially underdetermined and 'flew' does not distinguish the two senses.
Not-neutral query
FieldValue
QueryIs 'Brown bat has wings' neutral or not neutral?
Logic verdictInconclusive
NLI labelEntailment
Neutral classificationNot Neutral
Agents match✗
MCQ correct✗
Quality flagCONFLICT
Agents diverge in the same way as the conclusive item. The conflict arises because the logic agent's failure to disambiguate propagates to the synthesis, producing a conditional answer that does not match the dataset's definitive not-neutral annotation.
Flag rationale: Logic agent fails to apply mutual-exclusion disambiguation via query predicate — KB enrichment or logic agent improvement needed.
nail — A homonymous entity spanning fingernail and construction-nail senses
Nail is part of a finger. Nail is used in construction. Nails contain keratin. Nails have a pointed tip. Keratin is not a pointed tip. Pointed tips are not keratin. Nails can grow. There is a pink nail. Pink nail did not fasten the object.
Query typeLogicNLIMatchMCQ ✓Flag
InconclusiveInconclusiveNeutral✓✓GOLD
ConclusiveTrueNeutral✗✓REVIEW
NeutralInconclusiveNeutral✓✓GOLD
Not-neutralTrueNeutral✗✗REVIEW
paper — A homonymous entity spanning physical writing-material and academic-document senses
Paper is a writing material. Paper is an academic document. Papers contain cellulose fibers. Papers have research findings. Cellulose fibers are not research findings. Research findings are not cellulose fibers. Papers can be published. There is a yellow paper. Yellow paper was reviewed.
Query typeLogicNLIMatchMCQ ✓Flag
InconclusiveInconclusiveEntailment✗✗CONFLICT
ConclusiveTrueEntailment✓✓GOLD
NeutralTrueEntailment✓✗CONFLICT
Not-neutralTrueEntailment✓✓GOLD
bank — A homonymous entity spanning financial-institution and riverbank senses
Bank is a financial institution. Bank is the edge of a river. Banks have accounts. Banks have soil deposits. Accounts are not soil deposits. Soil deposits are not accounts. Banks can hold money. There is a green bank. Green bank eroded.
Query typeLogicNLIMatchMCQ ✓Flag
InconclusiveInconclusiveNeutral✓✓GOLD
ConclusiveInconclusiveContradiction✗✗REVIEW
NeutralInconclusiveNeutral✓✓GOLD
Not-neutralFalseContradiction✓✓REVIEW

bank/not: agents agree on Not Neutral but via Contradiction reasoning (riverbank sense dominant) rather than Entailment (financial-institution confirmed) — the classification is correct but the reasoning path diverges from the dataset's intended logic.

mouse — A homonymous entity spanning small-rodent and computer-device senses
Mouse is a small rodent. Mouse is a computer device. Mice have whiskers. Mice have buttons. Whiskers are not buttons. Buttons are not whiskers. Mice can click. There is a black mouse. Black mouse moved quickly.
Query typeLogicNLIMatchMCQ ✓Flag
InconclusiveInconclusiveNeutral✓✓GOLD
ConclusiveInconclusiveNeutral✓✗CONFLICT
NeutralInconclusiveNeutral✓✓GOLD
Not-neutralInconclusiveNeutral✓✗CONFLICT

Most diagnostic failure: both agents fail mouse/con and mouse/not, agree with each other, and do so with high confidence. Neither applies the whiskers≠buttons mutual-exclusion chain as a disambiguation trigger.

pitcher — A homonymous entity spanning baseball-player and liquid-container senses
Pitcher is a baseball player. Pitcher is a container for liquids. Pitchers have throwing arms. Pitchers have handles. Throwing arms are not handles. Handles are not throwing arms. Pitchers can throw. There is a blue pitcher. Blue pitcher was on the mound.
Query typeLogicNLIMatchMCQ ✓Flag
InconclusiveInconclusiveNeutral✓✓GOLD
ConclusiveInconclusiveNeutral✓✗REVIEW
NeutralInconclusiveNeutral✓✓GOLD
Not-neutralTrueEntailment✓✓GOLD
wave — A homonymous entity spanning water-movement and hand-gesture senses
Wave is a water movement. Wave is a hand gesture. Waves contain water molecules. Waves have friendly intent. Water molecules are not friendly intent. Friendly intent is not water molecules. Waves can crash. There is a red wave. Red wave approached.
Query typeLogicNLIMatchMCQ ✓Flag
InconclusiveInconclusiveNeutral✓✓GOLD
ConclusiveTrueNeutral✗✓REVIEW
NeutralInconclusiveNeutral✓✓GOLD
Not-neutralTrueEntailment✓✓GOLD

Cross-Key Observations

The inconclusive and neutral_query items are consistently handled well across all 8 keys: agent agreement is high (16/16 GOLD) because the contextual observation predicates ('flew', 'made decisions', 'eroded', 'moved quickly', 'was on the mound', 'approached') are genuinely non-discriminating, and both agents correctly identify referential underdetermination.

The most challenging query types are conclusive and not_neutral, which require agents to apply mutual-exclusion axioms as disambiguation triggers — a capability that only partially manifests: the NLI agent applies the chain for bat but both agents fail for mouse and pitcher/con.

Equivocation is the universal fallacy across all 32 items, reflecting the deliberate KB design. The KB universal property scoping flaw (properties asserted for all senses rather than per-sense) is the leading cause of CONFLICT flags, systematically affecting head, nail, paper, and wave conclusive/not_neutral items.

Logic ↔ NLI Correspondence Analysis

Logic and NLI agents agree in 23 of 32 items (71.9%), with systematic divergence patterns across two distinct failure modes.

This asymmetry reflects a fundamental difference in how the two systems handle scope: formal logic under CWA propagates universal KB facts to specific instances immediately, while NLI's monotonicity reasoning is more sensitive to contextual cues.

Fallacy Analysis

Equivocation is the universal root cause across all 32 items, reflecting the deliberate introduction of polysemous entities. Hasty Generalization appears in 22 items as a latent risk — the contextual observation predicate could be, but is not, used as definitive evidence for one sense. Affirming the Consequent appears in 16 items in the same latent-risk capacity. Amphiboly appears in 5 items (head/con, head/not, nail/not, wave/inc, wave/con) where natural language predicates carry structural ambiguity beyond the equivocation on the main noun. False Premise appears in 2 nail items because the KB asserts 'Pointed tips are not keratin' as an axiom, embedding an empirical claim.

Dataset Quality Assessment

Of the 32 items, 18 receive GOLD flags (56.3%), 7 receive REVIEW (21.9%), and 7 receive CONFLICT (21.9%), with no ERROR flags. GOLD items concentrate in inconclusive and neutral_query types. REVIEW items arise where one agent reaches the correct verdict via a spurious path. CONFLICT items arise from two sources:

  1. KB universal scoping flaws that cause agents to derive True/Entailment where the dataset annotates Inconclusive/Neutral (head/con, head/not, paper/inc, paper/neu).
  2. Systematic agent failure to apply mutual-exclusion disambiguation in both agents simultaneously (mouse/con, mouse/not, bat/not).

Resolution requires either sense-scoped KB property assertions (source 1) or explicit query-predicate disambiguation hooks in the agent prompts (source 2). The dataset's conceptual design is sound; the KB implementation needs refinement for approximately 4 keys (head, paper, mouse, and wave).

Methodology Notes