Triple
T9761357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Établissement public d’aménagement de La Défense |
E236677
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | établissement public d’aménagement |
C26190
|
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: établissement public d’aménagement Context triple: [Établissement public d’aménagement de La Défense, instanceOf, établissement public d’aménagement]
-
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.
municipal organization
A municipal organization is a local government entity responsible for providing public services, managing community resources, and implementing policies within a city, town, or other local jurisdiction.
-
C.
municipal property
Municipal property is any land, buildings, infrastructure, or other assets owned, leased, or otherwise controlled by a local government for public use or municipal operations.
-
D.
urban public space
An urban public space is a publicly accessible area within a city—such as streets, parks, plazas, and squares—designed or used for social interaction, movement, recreation, and civic life.
-
E.
administrative arrondissement
An administrative arrondissement is a territorial subdivision within a country or region used for local governance, administration, and statistical organization.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:25 p.m.