Triple

T15721021
Position Surface form Disambiguated ID Type / Status
Subject Prince Ivan Nikitich Odoevsky E381092 entity
Predicate givenName P17 FINISHED
Object Ivan E157814 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: Ivan | Statement: [Prince Ivan Nikitich Odoevsky, givenName, Ivan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ivan
Context triple: [Prince Ivan Nikitich Odoevsky, givenName, Ivan]
  • A. Ivan chosen
    Ivan is a common Slavic male given name widely used in Russia and other Eastern European countries, equivalent to "John" in English.
  • B. Ivan Vorotynsky
    Ivan Vorotynsky was a Russian noble and statesman who belonged to the influential group of aristocrats known as the Seven Boyars during the Time of Troubles.
  • C. Vasily
    Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • D. Fyodor
    Fyodor is a masculine given name of Russian origin, most famously borne by the novelist Fyodor Dostoevsky.
  • E. Pyotr
    Pyotr is the Russian given name of Peter Kropotkin, the influential 19th-century anarchist philosopher, geographer, and revolutionary.
  • 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_69d86d9bf930819082b30cf6d169297c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e04fb0b51081908e652ec4992296fa completed April 16, 2026, 2:55 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffc3b205dc81908c4194a931d94074 completed May 9, 2026, 11:30 p.m.
Created at: April 10, 2026, 4:45 a.m.