Triple
T10204828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Musta'in |
E242166
|
entity |
| Predicate | chronologicalOrderAsCaliph |
P50071
|
FINISHED |
| Object | 12th Abbasid caliph |
—
|
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: 12th Abbasid caliph | Statement: [al-Musta'in, chronologicalOrderAsCaliph, 12th Abbasid caliph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalOrderAsCaliph Context triple: [al-Musta'in, chronologicalOrderAsCaliph, 12th Abbasid caliph]
-
A.
caliphOrder
chosen
Indicates that one entity holds the position of caliph immediately before or after another entity in a historical or religious succession order.
-
B.
caliphalOrder
Indicates that an action or state occurs by decree, command, or authoritative directive of a caliph.
-
C.
associatedCaliph
Indicates a relationship where an entity is linked or connected to a specific caliph, typically through rule, patronage, affiliation, or historical association.
-
D.
caliphatePeriod
Indicates the time span during which a caliphate held authority or was in effect.
-
E.
caliphateStart
Indicates the point in time or event at which a particular caliphate begins or is established.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa22071c819095febd18dd607978 |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 10:29 a.m.