Triple
T33244995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Muwaffaq |
E851071
|
entity |
| Predicate | consolidatedPowerUnder |
P6502
|
FINISHED |
| Object | Abbasid Caliphate |
—
|
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: Abbasid Caliphate | Statement: [al-Muwaffaq, consolidatedPowerUnder, Abbasid Caliphate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consolidatedPowerUnder Context triple: [al-Muwaffaq, consolidatedPowerUnder, Abbasid Caliphate]
-
A.
consolidatedUnder
Indicates that one entity has been merged into and is now formally part of another, typically larger or parent, entity.
-
B.
exclusivePower
Indicates that one entity holds sole authority or control over another entity or a specific domain, excluding others from sharing that power.
-
C.
subjectOfPower
Indicates that one entity holds authority, control, or influence over another entity.
-
D.
chancellorPower
Indicates that an entity holds the authoritative executive or administrative powers associated with the role of chancellor over another entity or domain.
-
E.
exercisedPowerOver
chosen
Indicates that one entity exerted control, influence, or authority over another entity.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:31 a.m.