Triple
T21208077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lümanda municipality |
E522641
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former municipality of Estonia |
C44361
|
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 Estonia Context triple: [Lümanda municipality, instanceOf, former municipality of Estonia]
-
A.
former municipality of Finland
A former municipality of Finland is an administrative region that once functioned as an independent local government unit but has since been merged with or incorporated into another municipality.
-
B.
county of Estonia
A county of Estonia is an administrative territorial unit that groups together several municipalities within Estonia for regional governance and coordination.
-
C.
region of Estonia
A region of Estonia is a defined geographical or administrative area within the country, characterized by shared cultural, historical, economic, or environmental features.
-
D.
former municipality of the Netherlands
A former municipality of the Netherlands is an administrative region that once functioned as an independent local government unit but has since been merged, reorganized, or dissolved under Dutch municipal reforms.
-
E.
municipality of Lithuania
A municipality of Lithuania is an administrative territorial unit that functions as a local government area responsible for providing public services, implementing national policies, and managing community affairs within its defined boundaries.
- F. None of above. chosen
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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:25 p.m.