Triple
T24648803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oriental region of Morocco |
E610190
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative region of Morocco |
C11564
|
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: administrative region of Morocco Context triple: [Oriental region of Morocco, instanceOf, administrative region of Morocco]
-
A.
former administrative region of Morocco
A former administrative region of Morocco is a previously defined territorial division within the country’s governance structure that has since been reorganized, merged, or replaced by a new regional framework.
-
B.
region of Morocco
chosen
A region of Morocco is an administrative territorial division that groups several provinces and prefectures under a regional council and governor to coordinate governance, development, and public services.
-
C.
province of Morocco
A province of Morocco is an administrative territorial division within the country, subordinate to a region, that encompasses multiple municipalities and rural communes for local governance and public administration.
-
D.
prefecture of Morocco
A prefecture of Morocco is an administrative division, typically urban-centered, governed by a wali and subordinate to a region, responsible for local governance, public services, and implementation of national policies within its territory.
-
E.
region of Algeria
A region of Algeria is a large administrative and geographic subdivision of the country that groups together several provinces sharing common economic, cultural, or environmental characteristics.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:33 a.m.