Triple
T32791560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamic State provinces |
E838642
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Islamic State administrative division |
C47465
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Islamic State administrative division Context triple: [Islamic State provinces, instanceOf, Islamic State administrative division]
-
A.
Islamic State province
chosen
An Islamic State province is an administrative and territorial division claimed by the Islamic State group, representing a regional branch that operates under its ideological, organizational, and strategic framework.
-
B.
Islamic State organ
An Islamic State organ is a formal component or institution of the Islamic State’s governance structure, responsible for carrying out specific administrative, religious, military, or propaganda functions within its self-declared caliphate.
-
C.
subdivision of Iraq
A subdivision of Iraq is an administrative region within the country, such as a governorate, district, or subdistrict, established for local governance and organizational purposes.
-
D.
Fulani Islamic state
A Fulani Islamic state is a political entity historically or conceptually governed by Fulani elites under Islamic law, combining Fulani cultural leadership with the religious, legal, and administrative frameworks of Islam.
-
E.
Governorate of Jordan
A Governorate of Jordan is a primary administrative division of the country, governed by an appointed governor and responsible for local administration, public services, and regional development within its defined geographic area.
- F. None of above.
Provenance (1 batch)
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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:14 a.m.