Triple
T31624532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estado Libre y Soberano de Puebla |
E806984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | entidad federativa |
C11281
|
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: entidad federativa Context triple: [Estado Libre y Soberano de Puebla, instanceOf, entidad federativa]
-
A.
Mexican state
A Mexican state is a primary administrative and political subdivision of Mexico, possessing its own constitution, government, and certain autonomous powers under the federal system.
-
B.
federal unit
chosen
A federal unit is a constituent political entity, such as a state or province, within a federal system that shares sovereignty with a central government while retaining certain autonomous powers.
-
C.
entidad territorial de Colombia
Una entidad territorial de Colombia es una división político-administrativa dotada de autonomía relativa para la gestión de sus intereses locales dentro del marco de la Constitución y la ley, como departamentos, distritos, municipios y territorios indígenas.
-
D.
federal territory
A federal territory is a geographic area under the direct jurisdiction and administration of a federal government, distinct from constituent states or provinces and typically lacking the same degree of self-governance.
-
E.
federative unit of Brazil
A federative unit of Brazil is a primary political and administrative division of the country—such as a state or the Federal District—with its own government, constitution, and limited autonomy under the Brazilian federal system.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:42 p.m.