Triple
T38075045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rundāle Municipality |
E950688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former municipality of Latvia |
C66543
|
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 Latvia Context triple: [Rundāle Municipality, instanceOf, former municipality of Latvia]
-
A.
former municipality of Estonia
A former municipality of Estonia is an administrative unit that once functioned as a local government area in Estonia but has since been merged, reorganized, or dissolved through administrative reform.
-
B.
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.
-
C.
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.
-
D.
region of Latvia
A region of Latvia is a territorial subdivision of the country characterized by shared historical, cultural, economic, and administrative features that distinguish it from other areas.
-
E.
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.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.