Triple
T7559239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asamblea Departamental de Cundinamarca |
E178751
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corporación político-administrativa |
C4671
|
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: corporación político-administrativa Context triple: [Asamblea Departamental de Cundinamarca, instanceOf, corporación político-administrativa]
-
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.
political entity
A political entity is an organized group or jurisdiction, such as a state, nation, or governing body, that holds authority to make and enforce collective decisions over a defined population and territory.
-
C.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
D.
autonomous community government
An autonomous community government is a regional governing body with constitutionally recognized self-governing powers to manage political, administrative, and fiscal affairs within its territory under a broader national framework.
-
E.
collective political entity
chosen
A collective political entity is an organized group of individuals or communities that exercises or claims shared authority, representation, and decision-making power within a defined political framework.
- 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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:50 p.m.