Triple
T7646243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conseil administratif de Versoix |
E173129
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autorité exécutive locale |
C39
|
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: autorité exécutive locale Context triple: [Conseil administratif de Versoix, instanceOf, autorité exécutive locale]
-
A.
district administration
District administration is the local governing and executive authority responsible for implementing government policies, managing public services, and coordinating development activities within a defined district.
-
B.
autonomous community government
An autonomous community government is a regional governing body with constitutionally recognized self-governing powers to manage political, administrative, and fiscal affairs within its territory under a broader national framework.
-
C.
local authority of France
A local authority of France is a decentralized public entity (such as a commune, department, or region) with its own elected council and administrative powers to manage local affairs within a defined territory under national law.
-
D.
system of local government
A system of local government is an organized framework of institutions, powers, and processes through which local authorities manage public services, enforce regulations, and represent community interests within a defined geographic area.
-
E.
municipality
chosen
A municipality is a local administrative unit, such as a city, town, or district, governed by elected officials and responsible for providing public services and regulations within its defined geographic area.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:58 p.m.