Triple
T7075531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan the Young |
E164807
|
entity |
| Predicate | reasonForLossOfHeirStatus |
P41735
|
FINISHED |
| Object | death before his father |
—
|
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: death before his father | Statement: [Ivan the Young, reasonForLossOfHeirStatus, death before his father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForLossOfHeirStatus Context triple: [Ivan the Young, reasonForLossOfHeirStatus, death before his father]
-
A.
reasonForLossOfSuccessionRights
chosen
Indicates the specific cause or circumstance that led to an individual losing their rights of succession.
-
B.
reasonForElimination
Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
-
C.
notPrimaryHeir
Indicates that the referenced person is explicitly not the main or principal heir in an inheritance or succession context.
-
D.
reasonForLossOfVote
Indicates the specific cause or circumstance that led to an entity losing its right or ability to vote.
-
E.
endOfReignReason
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
- 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4ce3d3c81908cbb912b256aadbf |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.