Triple

T3567571
Position Surface form Disambiguated ID Type / Status
Subject Ivan I of Moscow E75487 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: [Ivan I of Moscow, givenName, Ivan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ivan
Context triple: [Ivan I of Moscow, 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. Vasily
    Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • C. Fyodor
    Fyodor is a masculine given name of Russian origin, most famously borne by the novelist Fyodor Dostoevsky.
  • D. Pyotr
    Pyotr is the Russian given name of Peter Kropotkin, the influential 19th-century anarchist philosopher, geographer, and revolutionary.
  • E. Viktor
    Viktor is the given name of Viktor Frankl, the Austrian neurologist, psychiatrist, and Holocaust survivor who founded logotherapy and wrote "Man’s Search for Meaning."
  • 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_69ad85d512708190829c8b2d3a2ccfb8 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc0ab51d881908f004fae47ab09d9 completed March 8, 2026, 6:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69be4d59f188819093e3a6c7037593cf completed March 21, 2026, 7:48 a.m.
Created at: March 8, 2026, 3:21 p.m.