Triple
T26013747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Cundinamarca |
E646969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative territorial entity type |
C27954
|
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 territorial entity type Context triple: [municipality of Cundinamarca, instanceOf, administrative territorial entity type]
-
A.
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.
-
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.
administrative division collection
A collection of administrative divisions is an organized grouping of territorial units (such as states, provinces, or districts) that together represent a structured subdivision of a larger political or geographic entity.
-
D.
political entity category
A political entity category is a conceptual classification that groups together types of organized political units—such as states, provinces, municipalities, or international organizations—based on shared structural, legal, or functional characteristics.
-
E.
municipality type
chosen
A municipality type is a classification that defines the legal, administrative, or functional category of a local government unit (such as city, town, or village) within a given jurisdiction.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:02 a.m.