Triple
T872630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talal of Jordan |
E18846
|
entity |
| Predicate | succeededToThroneAfter |
P15383
|
FINISHED |
| Object | assassination of Abdullah I of Jordan |
—
|
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: assassination of Abdullah I of Jordan | Statement: [Talal of Jordan, succeededToThroneAfter, assassination of Abdullah I of Jordan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededToThroneAfter Context triple: [Talal of Jordan, succeededToThroneAfter, assassination of Abdullah I of Jordan]
-
A.
monarchSuccessor
chosen
Indicates that one monarch directly follows another in a royal line of succession.
-
B.
successorAsKingOfScotland
Indicates that one person becomes the next king of Scotland following another person's reign.
-
C.
successorAsKingOfEngland
Indicates that one person becomes the next King of England following another person's reign.
-
D.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
E.
successorAsKingOfBohemia
Indicates that one person became the next king of Bohemia after another person.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac97d0f88190b67fcb7fc058e4b9 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8b9b5c81909ac71904f8b8b5cd |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.