Triple
T9235212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hisham III |
E221919
|
entity |
| Predicate | endOfReignCoincidedWith |
P15555
|
FINISHED |
| Object | abolition of the Caliphate of Córdoba |
—
|
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: abolition of the Caliphate of Córdoba | Statement: [Hisham III, endOfReignCoincidedWith, abolition of the Caliphate of Córdoba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfReignCoincidedWith Context triple: [Hisham III, endOfReignCoincidedWith, abolition of the Caliphate of Córdoba]
-
A.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
B.
reignedFrom
Indicates the time period during which an entity held ruling authority or sovereignty over a domain.
-
C.
ended reign start year
Indicates the calendar year in which a ruler’s period of reign came to an end.
-
D.
endOfReignReason
chosen
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
-
E.
correspondsToReignOf
Indicates that something (such as a time period, event, or record) matches or is associated with the duration of a specific 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee1cca0c8190bf587f54236c9e45 |
completed | April 1, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:29 p.m.