Triple
T8974801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annecy agglomeration |
E214359
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | agglomeration community |
C12570
|
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: agglomeration community Context triple: [Annecy agglomeration, instanceOf, agglomeration community]
-
A.
metropolitan community
A metropolitan community is a densely populated urban area and its surrounding regions where people live, work, and interact within a shared economic, social, and infrastructural network.
-
B.
communauté d’agglomération
chosen
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.).
-
C.
urban island community
An urban island community is a densely populated, self-contained neighborhood or district surrounded by water within or adjacent to a city, blending metropolitan infrastructure with the social and environmental characteristics of island living.
-
D.
collective municipality
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.
-
E.
former community
A former community is a once-populated settlement or social group that has lost its residents or cohesion and no longer functions as an active community.
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:02 p.m.