Triple
T23660194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peseux |
E584421
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former municipality of the canton of Neuchâtel |
C30373
|
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: former municipality of the canton of Neuchâtel Context triple: [Peseux, instanceOf, former municipality of the canton of Neuchâtel]
-
A.
former municipality of Switzerland
chosen
A former municipality of Switzerland is an administrative entity that once functioned as an independent local government unit but has since been merged, dissolved, or reorganized within the Swiss municipal structure.
-
B.
municipality of the canton of Solothurn
A municipality of the canton of Solothurn is the smallest local administrative unit within the Swiss canton of Solothurn, responsible for local governance, public services, and community affairs within its defined territory.
-
C.
former canton of Switzerland
A former canton of Switzerland is a historical administrative region that once functioned as a semi-autonomous member state within the Swiss Confederation but has since been dissolved, merged, or reorganized.
-
D.
Swiss canton
A Swiss canton is a semi-sovereign federal state within Switzerland, possessing its own constitution, government, and legislative authority under the Swiss federal system.
-
E.
district of Switzerland
A district of Switzerland is an intermediate administrative subdivision within a canton that groups several municipalities for purposes such as local governance, judicial organization, and regional coordination.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:50 p.m.