Triple
T17331539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Projet d’agglomération franco-valdo-genevois |
E420828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | metropolitan planning instrument |
C22869
|
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: metropolitan planning instrument Context triple: [Projet d’agglomération franco-valdo-genevois, instanceOf, metropolitan planning instrument]
-
A.
spatial planning instrument
chosen
A spatial planning instrument is a formal tool, policy, or regulatory mechanism used by authorities to guide, control, and coordinate the use and development of land and space within a defined territory.
-
B.
metropolitan authority
A metropolitan authority is a governing body responsible for planning, coordinating, and managing public services and development across a large urban area and its surrounding municipalities.
-
C.
local and regional planning framework
A local and regional planning framework is a structured set of policies, processes, and tools that guide coordinated land use, infrastructure, and development decisions across municipalities and regions to achieve sustainable, equitable, and efficient growth.
-
D.
regional transport plan
A regional transport plan is a strategic framework that outlines long-term goals, policies, and coordinated investments for transportation systems across a defined geographic region.
-
E.
urban planning master plan
An urban planning master plan is a comprehensive, long-term framework that guides the physical, social, and economic development of a city or region through coordinated land use, infrastructure, and policy strategies.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:43 a.m.