Triple
T25487843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lüneburg (Regierungsbezirk) |
E638761
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former Regierungsbezirk |
C536
|
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 Regierungsbezirk Context triple: [Lüneburg (Regierungsbezirk), instanceOf, former Regierungsbezirk]
-
A.
former administrative territorial entity
chosen
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
-
B.
former rural district
A former rural district is an administrative subdivision that once governed a predominantly countryside area but has since been dissolved, merged, or restructured into a different territorial unit.
-
C.
administrative region of Bavaria
An administrative region of Bavaria is a territorial subdivision within the German state of Bavaria that serves as an intermediate level of government, coordinating regional administration, planning, and public services across its constituent districts and municipalities.
-
D.
former canton
A former canton is an administrative territorial unit that once functioned as a subdivision within a country’s governance structure but has since been dissolved, merged, or replaced by a new administrative arrangement.
-
E.
former district of Japan
A former district of Japan is an administrative subdivision that once existed within a prefecture but has since been dissolved or merged due to municipal reorganization.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:33 p.m.