Triple
T26428024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | règlements communaux de Versoix |
E664419
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | règlements communaux |
C5720
|
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: règlements communaux Context triple: [règlements communaux de Versoix, instanceOf, règlements communaux]
-
A.
communauté urbaine
Une communauté urbaine est un établissement public de coopération intercommunale français qui regroupe plusieurs communes formant un ensemble urbain continu afin de mutualiser des compétences et des services à l’échelle de l’agglomération.
-
B.
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.).
-
C.
commune urbaine
A "commune urbaine" is an administrative municipality characterized by a predominantly urban environment, higher population density, and developed infrastructure and services.
-
D.
municipal ordinance
chosen
A municipal ordinance is a local law or regulation enacted by a city or town government to govern conduct, land use, public safety, and other matters within its jurisdiction.
-
E.
rural commune
A rural commune is a small, self-governing community in a countryside area, typically organized around shared resources, local agriculture, and collective decision-making.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:47 p.m.