Triple

T21958821
Position Surface form Disambiguated ID Type / Status
Subject Mitsubishi A7M Reppū E542265 entity
Predicate designGoal P79 FINISHED
Object superior performance to A6M Zero NE NERFINISHED

How this triple was built (3 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: superior performance to A6M Zero | Statement: [Mitsubishi A7M Reppū, designGoal, superior performance to A6M Zero]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: superior performance to A6M Zero
Context triple: [Mitsubishi A7M Reppū, designGoal, superior performance to A6M Zero]
  • A. Mitsubishi A6M Zero fighters
    The Mitsubishi A6M Zero fighters were highly maneuverable, long-range carrier-based Japanese fighter aircraft that dominated early World War II Pacific air combat.
  • B. Mitsubishi A6M
    The Mitsubishi A6M, commonly known by its Allied reporting name "Zeke" or "Zero," was a highly maneuverable Japanese carrier-based fighter aircraft used extensively during World War II.
  • C. Albatros fighter aircraft
    The Albatros fighter aircraft were German World War I biplane fighters, notably used by aces, that combined streamlined wooden monocoque fuselages with powerful engines to achieve high speed and maneuverability.
  • D. Mitsubishi A5M fighters
    The Mitsubishi A5M fighters were Japanese carrier-based monoplane fighters used by the Imperial Japanese Navy in the late 1930s and early World War II, notable as the predecessor to the famed A6M Zero.
  • E. Mitsubishi A7M Reppū design
    The Mitsubishi A7M Reppū design was a late-World War II Japanese carrier-based fighter project intended as the high-performance successor to the famed A6M Zero.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: superior performance to A6M Zero
Target entity description: "Superior performance to A6M Zero" refers to the design objective for the Mitsubishi A7M Reppū, a late-World War II Japanese carrier-based fighter intended to surpass the famed A6M Zero in speed, maneuverability, and overall combat capability.
  • A. Mitsubishi A6M Zero fighters
    The Mitsubishi A6M Zero fighters were highly maneuverable, long-range carrier-based Japanese fighter aircraft that dominated early World War II Pacific air combat.
  • B. Mitsubishi A6M
    The Mitsubishi A6M, commonly known by its Allied reporting name "Zeke" or "Zero," was a highly maneuverable Japanese carrier-based fighter aircraft used extensively during World War II.
  • C. Albatros fighter aircraft
    The Albatros fighter aircraft were German World War I biplane fighters, notably used by aces, that combined streamlined wooden monocoque fuselages with powerful engines to achieve high speed and maneuverability.
  • D. Mitsubishi A5M fighters
    The Mitsubishi A5M fighters were Japanese carrier-based monoplane fighters used by the Imperial Japanese Navy in the late 1930s and early World War II, notable as the predecessor to the famed A6M Zero.
  • E. Mitsubishi A7M Reppū design chosen
    The Mitsubishi A7M Reppū design was a late-World War II Japanese carrier-based fighter project intended as the high-performance successor to the famed A6M Zero.
  • F. None of above.

Provenance (2 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69e0c47fab1081908dc74a6545dbb051 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1244204f081909742d4fe138610d6 completed April 28, 2026, 9:18 p.m.
Created at: April 16, 2026, 8 p.m.