Triple

T15560849
Position Surface form Disambiguated ID Type / Status
Subject Simeon of Moscow E370992 entity
Predicate nobleFamily P914 FINISHED
Object Daniilovichi
Daniilovichi was the ruling dynasty of Moscow’s princes and grand princes, descended from Daniil Aleksandrovich, that laid the foundations for the rise of the Grand Duchy of Moscow.
 E188958 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: Daniilovichi | Statement: [Simeon of Moscow, nobleFamily, Daniilovichi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Daniilovichi
Context triple: [Simeon of Moscow, nobleFamily, Daniilovichi]
  • A. Danilovich
    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. Vasilyev
    Vasilyev is a common Russian surname typically used in its masculine form.
  • D. Shchusev
    Shchusev is a Russian surname most notably associated with Alexey Shchusev, a prominent Soviet architect known for designing Lenin's Mausoleum in Moscow.
  • E. Zinoviy
    Zinoviy is a masculine given name of Slavic origin, commonly used in Russian and Ukrainian contexts.
  • 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: Daniilovichi
Triple: [Simeon of Moscow, nobleFamily, Daniilovichi]
Generated description
Daniilovichi was the ruling dynasty of Moscow’s princes and grand princes, descended from Daniil Aleksandrovich, that laid the foundations for the rise of the Grand Duchy of Moscow.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Daniilovichi
Target entity description: Daniilovichi was the ruling dynasty of Moscow’s princes and grand princes, descended from Daniil Aleksandrovich, that laid the foundations for the rise of the Grand Duchy of Moscow.
  • 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. Vasilyev
    Vasilyev is a common Russian surname typically used in its masculine form.
  • D. Shchusev
    Shchusev is a Russian surname most notably associated with Alexey Shchusev, a prominent Soviet architect known for designing Lenin's Mausoleum in Moscow.
  • E. Zinoviy
    Zinoviy is a masculine given name of Slavic origin, commonly used in Russian and Ukrainian contexts.
  • F. None of above.

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_69d85cc6cf40819091f4a5facee1ebe6 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ddb4c0c81909b3f4c75c91f7f3f completed April 16, 2026, 2:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff456821988190971539b683f6c656 completed May 9, 2026, 2:32 p.m.
NEDg Description generation batch_69ff46f44b2c81909f65f0ab455c6549 completed May 9, 2026, 2:38 p.m.
NED2 Entity disambiguation (via description) batch_69ff477a63b48190a453cf669dfda228 completed May 9, 2026, 2:40 p.m.
Created at: April 10, 2026, 4:09 a.m.