Triple
T3292490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Godunov |
E69131
|
entity |
| Predicate | riseLinkedTo |
P47789
|
FINISHED |
| Object | childlessness of Tsar Fyodor I |
—
|
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: childlessness of Tsar Fyodor I | Statement: [House of Godunov, riseLinkedTo, childlessness of Tsar Fyodor I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riseLinkedTo Context triple: [House of Godunov, riseLinkedTo, childlessness of Tsar Fyodor I]
-
A.
raisedFrom
Indicates that one entity has been elevated, derived, or brought up from another prior state, source, or condition.
-
B.
risesIn
Indicates that a river or similar watercourse originates or begins its flow in a specified location.
-
C.
raisedWith
Indicates that two or more entities grew up together in the same household or close environment during their formative years.
-
D.
raisedBy
Indicates that one entity has been brought up, nurtured, or reared under the care, guidance, or authority of another entity.
-
E.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
- F. None of above. chosen
Provenance (4 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb07379dc8190b7bb409bcf42bdd6 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:10 p.m.