Triple
T6744421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vevey–Montreux agglomeration |
E154173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | agglomeration |
C61
|
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 Context triple: [Vevey–Montreux agglomeration, instanceOf, agglomeration]
-
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.
metropolitan area
chosen
A metropolitan area is a densely populated urban region consisting of a central city and its surrounding suburbs and satellite communities, linked by economic, social, and infrastructural ties.
-
C.
urban ensemble
An urban ensemble is a cohesive grouping of buildings, public spaces, and infrastructure whose combined form, function, and character create a distinct, perceivable urban identity.
-
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.
urban-type settlement
An urban-type settlement is a semi-urban locality that exhibits some characteristics of a town or small city—such as concentrated housing, infrastructure, and non-agricultural employment—without meeting all the criteria for full city status.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:10 p.m.