Triple

T33896747
Position Surface form Disambiguated ID Type / Status
Subject Feodor I of Russia E868929 entity
Predicate reasonForCauseOfHistoricalEvent P15033 FINISHED
Object died without an heir 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: died without an heir | Statement: [Feodor I of Russia, reasonForCauseOfHistoricalEvent, died without an heir]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForCauseOfHistoricalEvent
Context triple: [Feodor I of Russia, reasonForCauseOfHistoricalEvent, died without an heir]
  • A. historicalReason chosen
    Indicates that one entity exists, occurs, or is justified because of causes, events, or circumstances rooted in the past of another entity.
  • B. historicalEventsDescribed
    Indicates that one entity (such as a document, text, or account) describes or recounts the historical events associated with another entity.
  • C. reasonForEvent
    Indicates that one event occurs as a consequence of, or is motivated or explained by, another specified cause or reason.
  • D. historicalEventDescribedAs
    Indicates that a historical event is characterized or portrayed using a particular description, label, or narrative.
  • E. impactOfNotableEvent
    Indicates the causal influence or consequences that a specific notable event has on an entity, situation, or outcome.
  • 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_69f34997703c8190866b1d404bce531f completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fd7b0503a08190ba07338365b6fcc9 completed May 8, 2026, 5:56 a.m.
PD Predicate disambiguation batch_69fd7a9733dc81909199f453c0cc2bc1 completed May 8, 2026, 5:54 a.m.
Created at: May 1, 2026, 1:48 a.m.