Triple
T33449287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verwaltungsgemeinschaft Vorharz |
E856592
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former collective municipality |
C13569
|
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 collective municipality Context triple: [Verwaltungsgemeinschaft Vorharz, instanceOf, former collective municipality]
-
A.
former local municipality
A former local municipality is an administrative area that once had its own local government authority but has since been dissolved, merged, or restructured into a different governing entity.
-
B.
collective municipality
chosen
A collective municipality is an administrative unit comprising several smaller municipalities that collaborate to share services and governance functions while retaining their individual local identities.
-
C.
former rural municipality
A former rural municipality is a previously independent local administrative unit in a countryside or non-urban area that has since been dissolved, merged, or reorganized into another jurisdiction.
-
D.
former municipal government
A former municipal government is a previously existing local governing body or administrative authority that has been dissolved, merged, or replaced and no longer exercises official jurisdiction over its former municipality.
-
E.
former upper-tier municipality
A former upper-tier municipality is a previously existing regional or county-level local government entity that once coordinated and provided services for multiple lower-tier municipalities but has since been dissolved, restructured, or replaced.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:37 a.m.