Triple
T11312425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Communauté urbaine du Grand Reims |
E267871
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | communauté urbaine |
C29540
|
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: communauté urbaine Context triple: [Communauté urbaine du Grand Reims, instanceOf, communauté urbaine]
-
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 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.
-
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.
city
A city is a densely populated, structured urban area characterized by extensive infrastructure, diverse economic activities, and complex social, cultural, and political systems.
-
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. chosen
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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:32 p.m.