Triple

T9568684
Position Surface form Disambiguated ID Type / Status
Subject Ivan Kozhedub E230855 entity
Predicate familyName P18 FINISHED
Object Kozhedub E230855 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: Kozhedub | Statement: [Ivan Kozhedub, familyName, Kozhedub]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kozhedub
Context triple: [Ivan Kozhedub, familyName, Kozhedub]
  • A. Kozhedub chosen
    Kozhedub is a Slavic surname most famously borne by Ivan Kozhedub, a highly decorated Soviet World War II fighter ace.
  • B. Kornienko
    Kornienko is a Ukrainian surname most notably borne by Oleksandr Kornienko, a contemporary Ukrainian politician and public figure.
  • C. Kozlov
    Kozlov is a historic Russian town, now known as Michurinsk, that developed as a significant regional center of trade and agriculture.
  • D. Kozlov
    Kozlov is the former Russian name of the city now known as Gözleve (Eupatoria) in Crimea, reflecting its historical period under Russian influence.
  • E. Kozmodemyansk
    Kozmodemyansk is a historic town in the Mari El Republic of Russia, situated on the Volga River and known for its traditional Mari culture and wooden architecture.
  • 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_69ca847f22188190a56e4a97625bef22 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9987cb0c8190af32a1193de54890 completed April 1, 2026, 10:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69d152b5b40c81909a84e34a944abfd0 completed April 4, 2026, 6:04 p.m.
Created at: March 30, 2026, 8:04 p.m.