Triple

T10016357
Position Surface form Disambiguated ID Type / Status
Subject Ivan Ilyich Golovin E199505 entity
Predicate familyName P18 FINISHED
Object Golovin
Golovin is a Russian surname historically borne by various notable figures in politics, the military, and the arts.
 E835102 NE FINISHED

How this triple was built (4 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: Golovin | Statement: [Ivan Ilyich Golovin, familyName, Golovin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Golovin
Context triple: [Ivan Ilyich Golovin, familyName, Golovin]
  • A. Golymin
    Golymin is a village in east-central Poland best known as the site of a significant engagement during the Napoleonic Wars.
  • B. Malinovsky
    Malinovsky is a Russian surname most notably associated with Soviet military commander and Marshal of the Soviet Union Rodion Malinovsky.
  • 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. Tolbukhin
    Tolbukhin is a Russian surname most notably associated with Soviet military commander Fyodor Tolbukhin, a prominent general during World War II.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Golovin
Triple: [Ivan Ilyich Golovin, familyName, Golovin]
Generated description
Golovin is a Russian surname historically borne by various notable figures in politics, the military, and the arts.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Golovin
Target entity description: Golovin is a Russian surname historically borne by various notable figures in politics, the military, and the arts.
  • A. Golymin
    Golymin is a village in east-central Poland best known as the site of a significant engagement during the Napoleonic Wars.
  • B. Malinovsky
    Malinovsky is a Russian surname most notably associated with Soviet military commander and Marshal of the Soviet Union Rodion Malinovsky.
  • 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. Tolbukhin
    Tolbukhin is a Russian surname most notably associated with Soviet military commander Fyodor Tolbukhin, a prominent general during World War II.
  • F. None of above. chosen

Provenance (5 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_69ca8315a1a08190ab310f25620f362b completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cdcd4ad3348190bae03cd37c787674 completed April 2, 2026, 1:58 a.m.
NED1 Entity disambiguation (via context triple) batch_69d26a99971081908397f06c0ce913d0 completed April 5, 2026, 1:58 p.m.
NEDg Description generation batch_69d26c20f50081909a8a3b4530dc5fc0 completed April 5, 2026, 2:05 p.m.
NED2 Entity disambiguation (via description) batch_69d26caee48481909d085b8df7ce14ab completed April 5, 2026, 2:07 p.m.
Created at: March 30, 2026, 8:53 p.m.