Triple
T34397553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbasid invasion of Anatolia in 838 |
E882873
|
entity |
| Predicate | caliph |
P17619
|
FINISHED |
| Object | al-Mu'tasim |
—
|
NE NERFINISHED |
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: al-Mu'tasim | Statement: [Abbasid invasion of Anatolia in 838, caliph, al-Mu'tasim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caliph Context triple: [Abbasid invasion of Anatolia in 838, caliph, al-Mu'tasim]
-
A.
caliphate
Indicates a relationship in which an authority or governance structure is organized under a caliph, claiming religious and political leadership over a Muslim community or territory.
-
B.
associatedCaliph
chosen
Indicates a relationship where an entity is linked or connected to a specific caliph, typically through rule, patronage, affiliation, or historical association.
-
C.
primaryCaliph
Indicates that one entity serves as the main or first-recognized caliph (successor/leader) in relation to another entity.
-
D.
servedCaliph
Indicates that one entity acted in service to, or under the authority of, a caliph.
-
E.
caliphalTitle
Indicates that an entity holds or is designated by a title associated with a caliph or the caliphate.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.