Triple

T8977342
Position Surface form Disambiguated ID Type / Status
Subject Ivan Kalita E214424 entity
Predicate memberOfDynasty P1547 FINISHED
Object Daniilovichi E188958 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: Daniilovichi | Statement: [Ivan Kalita, memberOfDynasty, Daniilovichi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Daniilovichi
Context triple: [Ivan Kalita, memberOfDynasty, Daniilovichi]
  • A. Danilovich chosen
    Danilovich is a Russian patronymic indicating "son of Danilo," commonly used as a middle name in Slavic naming traditions.
  • B. Semyonov
    Semyonov is a common Russian surname borne by numerous notable figures in fields such as literature, science, and military history.
  • C. Romanovich
    Romanovich is a Slavic patronymic surname indicating descent from a man named Roman, historically associated with Eastern European nobility such as the rulers of Galicia.
  • D. Vasilevsky
    Vasilevsky is a Russian surname most prominently associated with Aleksandr Vasilevsky, a leading Soviet military commander and Marshal of the Soviet Union during World War II.
  • E. Volfovich
    Volfovich is the patronymic derived from the given name of Vladimir Zhirinovsky’s father, used as part of the Russian politician’s full name.
  • 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_69ca839ea8b88190922c6a326ffcc0d3 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc67a33c8481909125acf4b7f0a919 completed April 1, 2026, 12:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfc96e7eb48190a3df410b1544b997 completed April 3, 2026, 2:06 p.m.
Created at: March 30, 2026, 7:02 p.m.