Triple
T31175082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hallbergmoos |
E794721
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality of Bavaria |
C55261
|
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 Bavaria Context triple: [Hallbergmoos, instanceOf, municipality of Bavaria]
-
A.
municipality of Baden-Württemberg
A municipality of Baden-Württemberg is a local administrative unit within the German federal state of Baden-Württemberg, responsible for self-governance and public services in its defined geographic area.
-
B.
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.
-
C.
local municipality in Germany
chosen
A local municipality in Germany is the smallest self-governing administrative unit responsible for local public services, planning, and community affairs within a defined geographic area.
-
D.
borough of Munich
A borough of Munich is an administrative subdivision of the city that encompasses specific neighborhoods and local governance functions within Munich’s overall municipal structure.
-
E.
region of Bavaria
A region of Bavaria is a geographically and administratively defined area within the German federal state of Bavaria, characterized by shared cultural, historical, and economic features.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:07 p.m.