Triple

T16137263
Position Surface form Disambiguated ID Type / Status
Subject Ivan II of Moscow E391562 entity
Predicate dynasticSuccessionPosition P64352 FINISHED
Object son and heir of Ivan I of Moscow LITERAL 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: son and heir of Ivan I of Moscow | Statement: [Ivan II of Moscow, dynasticSuccessionPosition, son and heir of Ivan I of Moscow]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dynasticSuccessionPosition
Context triple: [Ivan II of Moscow, dynasticSuccessionPosition, son and heir of Ivan I of Moscow]
  • A. dynasticRole
    Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
  • B. dynasticSeat
    Indicates that a particular location serves as the principal seat of power or ruling center for a specific dynasty or ruling family.
  • C. successorDynastyOrigin
    Indicates the place or cultural-geographic origin from which a successor dynasty arises in relation to its predecessor.
  • D. monarchSuccessor
    Indicates that one monarch directly follows another in a royal line of succession.
  • E. isNextInLineOfSuccessionTo chosen
    Indicates that one entity is the immediate heir or successor designated to take over a position, title, or role when the current holder can no longer occupy it.
  • F. None of above.

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_69d87f1bb0988190b490d273dbf3fd03 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e21a05e68881908319454a478cdda5 completed April 17, 2026, 11:31 a.m.
PD Predicate disambiguation batch_69e182885bc08190822ae7e8a4b8ac1f completed April 17, 2026, 12:44 a.m.
Created at: April 10, 2026, 5:01 a.m.