Triple
T341467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umayyad Caliphate |
E6845
|
entity |
| Predicate | establishedAsCaliphate |
P5762
|
FINISHED |
| Object | after First Fitna |
—
|
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: after First Fitna | Statement: [Umayyad Caliphate, establishedAsCaliphate, after First Fitna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsCaliphate Context triple: [Umayyad Caliphate, establishedAsCaliphate, after First Fitna]
-
A.
conquestYear
Indicates the year in which one entity successfully conquered or took control over another entity.
-
B.
reunifiedAsCapitalInYear
Indicates that an entity regained its status as a capital city in a specified year after a period of not holding that status.
-
C.
establishedAs
chosen
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
D.
reasonForStartOfReign
Indicates the cause, circumstance, or event that led to the beginning of an entity’s reign.
-
E.
abdicatedInFavorOf
Indicates that one entity has voluntarily renounced a position, role, or right so that another specific entity may assume it.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae611f88190955fbebe2b01835b |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95197fc8190820e8ebd0d7d27fa |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.