Triple

T14158592
Position Surface form Disambiguated ID Type / Status
Subject Mark III E350875 entity
Predicate successor P78 FINISHED
Object Mark IV E432423 NE FINISHED

How this triple was built (2 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: Mark IV | Statement: [Mark III, successor, Mark IV]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Mark IV
Context triple: [Mark III, successor, Mark IV]
  • A. Mark III
    Mark III is one of Tony Stark’s early Iron Man armor suits, recognized for refining his initial design into a more advanced, weaponized, and iconic red-and-gold configuration.
  • B. Mark II
    Mark II is Tony Stark’s early silver-colored Iron Man armor prototype that served as the basis for later, more advanced suits.
  • C. Mark VIII
    The Mark VIII is a British World War I–era torpedo that became one of the Royal Navy’s standard submarine-launched torpedoes.
  • D. Mark-4
    Mark-4 is a fourth-generation Jaeger classification used in the Pacific Rim universe, denoting advanced combat robots like Crimson Typhoon.
  • E. Mark IV tank chosen
    The Mark IV tank was a British World War I armored fighting vehicle that became one of the first widely used tanks in combat, notably helping to pioneer large-scale mechanized warfare.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d8278775fc8190b0802d22ca2f495d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61377de48190a3470d28f0edd34a completed April 14, 2026, 3:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcf7ef4d80819098d210503f5d22e9 completed May 7, 2026, 8:37 p.m.
Created at: April 10, 2026, 12:58 a.m.