Triple
T16894284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interlaken-Oberhasli administrative district |
E424257
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative district of the canton of Bern |
C15919
|
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: administrative district of the canton of Bern Context triple: [Interlaken-Oberhasli administrative district, instanceOf, administrative district of the canton of Bern]
-
A.
district of Switzerland
chosen
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.
-
B.
district of Lausanne
A district of Lausanne is an administrative and geographic subdivision of the city that groups together neighborhoods for local governance, services, and community identity.
-
C.
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.
-
D.
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.
-
E.
region of Switzerland
A region of Switzerland is a geographically defined area within the country characterized by shared cultural, linguistic, economic, or natural features that distinguish it from other parts of Switzerland.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:29 a.m.