Triple
T30517187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobanî Canton |
E776597
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | de facto administrative division |
C740
|
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: de facto administrative division Context triple: [Kobanî Canton, instanceOf, de facto administrative division]
-
A.
administrative territorial entity
chosen
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
B.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
-
C.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
D.
traditional political subdivision
A traditional political subdivision is a historically established territorial unit within a country, such as a province, county, or parish, that serves administrative, legal, and governance functions.
-
E.
Second-level administrative division
A second-level administrative division is a territorial unit within a country that is directly below the primary (first-level) administrative regions, such as provinces or states, and typically manages local governance and public services.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:16 p.m.