Triple
T35801269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Saud of Saudi Arabia |
E1034983
|
entity |
| Predicate | endOfReignMechanism |
P15555
|
FINISHED |
| Object | formal abdication in favor of Faisal |
—
|
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: formal abdication in favor of Faisal | Statement: [King Saud of Saudi Arabia, endOfReignMechanism, formal abdication in favor of Faisal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfReignMechanism Context triple: [King Saud of Saudi Arabia, endOfReignMechanism, formal abdication in favor of Faisal]
-
A.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
B.
endOfReignReason
chosen
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
-
C.
endOfSecondReign
Indicates that a second period of rule or governance by an entity has concluded.
-
D.
appliesAfterReignOf
Indicates that something becomes relevant, valid, or in effect only after the reign or rule of a specified entity has ended.
-
E.
reignAfter
Indicates that one entity begins its reign or rule following the conclusion of another entity'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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.