Triple

T2464587
Position Surface form Disambiguated ID Type / Status
Subject Theodore E55214 entity
Predicate hasVariant P455 FINISHED
Object Fyodor E236337 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: Fyodor | Statement: [Theodore, hasVariant, Fyodor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fyodor
Context triple: [Theodore, hasVariant, Fyodor]
  • A. Fyodor chosen
    Fyodor is a masculine given name of Russian origin, most famously borne by the novelist Fyodor Dostoevsky.
  • B. Pyotr
    Pyotr is the Russian given name of Peter Kropotkin, the influential 19th-century anarchist philosopher, geographer, and revolutionary.
  • C. Alyosha Peshkov
    Alyosha Peshkov is the young, semi-autobiographical protagonist of Maxim Gorky’s novel "My Childhood," depicting his harsh upbringing and moral development in late 19th-century Russia.
  • D. Dmitry Ivanovich
    Dmitry Ivanovich was a late 15th-century Russian prince and one-time heir apparent to the throne of Muscovy during the reign of his grandfather Ivan III.
  • E. Vasily
    Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • 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_69ab49e3622c8190ad22afa2c4fbb807 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abd1216f44819094c46ae7c2c1e394 completed March 7, 2026, 7:17 a.m.
NED1 Entity disambiguation (via context triple) batch_69b4e4c13494819095821f44916329c9 completed March 14, 2026, 4:32 a.m.
Created at: March 6, 2026, 9:44 p.m.