Triple
T3908707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comunidade Intermunicipal do Douro |
E87269
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Comunidade Intermunicipal |
C13569
|
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: Comunidade Intermunicipal Context triple: [Comunidade Intermunicipal do Douro, instanceOf, Comunidade Intermunicipal]
-
A.
communauté d’agglomération
Une communauté d’agglomération est un établissement public de coopération intercommunale français qui regroupe plusieurs communes formant un ensemble de plus de 50 000 habitants autour d’une ou plusieurs villes-centres afin de mutualiser des compétences et services (aménagement, développement économique, transports, etc.).
-
B.
collective municipality
chosen
A collective municipality is an administrative unit comprising several smaller municipalities that collaborate to share services and governance functions while retaining their individual local identities.
-
C.
freguesia of Portugal
A freguesia of Portugal is the smallest administrative subdivision in the country, functioning as a civil parish with its own local government and community services within a municipality.
-
D.
district of Portugal
A district of Portugal is an administrative territorial division that groups several municipalities within a defined geographic area for governmental and statistical purposes.
-
E.
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.
- 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.