Triple
T5051734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viimsi Parish |
E113800
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality of Estonia |
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: municipality of Estonia Context triple: [Viimsi Parish, instanceOf, municipality of Estonia]
-
A.
municipality of Portugal
A municipality of Portugal is an administrative division governed by a municipal council and mayor, responsible for local governance, public services, and community development within its defined territorial area.
-
B.
municipality of Belgium
A municipality of Belgium is the smallest administrative division in the country, governed by a local council and mayor, responsible for providing public services and local regulations within its defined territory.
-
C.
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.
-
D.
special municipality of the Netherlands
A special municipality of the Netherlands is a public body in the Caribbean that is directly administered by the Dutch central government but is not part of any Dutch province.
-
E.
national library of Estonia component
A national library of Estonia component represents any structural, functional, or informational part of the National Library of Estonia, such as its collections, services, departments, or digital systems, within a larger library management or architectural model.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:37 p.m.