Triple
T38704030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Est Ensemble |
E950214
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public territorial intercommunal structure |
C52402
|
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: public territorial intercommunal structure Context triple: [Est Ensemble, instanceOf, public territorial intercommunal structure]
-
A.
territorial collectivity component
A territorial collectivity component is an administrative subdivision or unit that forms part of a larger territorial collectivity, possessing defined geographic boundaries and specific governance responsibilities within that broader entity.
-
B.
commune-level administrative unit
A commune-level administrative unit is the smallest local government division within a country, typically responsible for basic public services, local regulations, and community administration for a town, village, or small group of settlements.
-
C.
regional municipal structure
chosen
A regional municipal structure is an organized framework that coordinates governance, services, and planning across multiple municipalities within a defined geographic area.
-
D.
administrative territorial entity
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
E.
territorial district
A territorial district is a defined geographic area within a larger region or country, established for administrative, political, legal, or organizational purposes.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.