Triple
T10212195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lirey |
E242355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commune déléguée |
C11280
|
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: commune déléguée Context triple: [Lirey, instanceOf, commune déléguée]
-
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.
commune in France
chosen
A commune in France is the smallest administrative division, functioning as a local municipality with its own mayor and council responsible for local governance and public services.
-
C.
district-level people’s committee
A district-level people’s committee is a local executive governing body responsible for implementing laws, policies, and administrative decisions within a specific district under the authority of higher-level state institutions.
-
D.
commune-level administrative unit
A commune-level administrative unit is the smallest local government division within a country, typically responsible for basic public services, local regulations, and community administration for a town, village, or small group of settlements.
-
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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:02 a.m.