Triple
T9146393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berg (Starnberg district) |
E219466
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality in Bavaria |
C13487
|
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 in Bavaria Context triple: [Berg (Starnberg district), instanceOf, municipality in Bavaria]
-
A.
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.
-
B.
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.
-
C.
town in Germany
chosen
A town in Germany is a moderately sized, legally defined urban municipality that serves as a local administrative, economic, and cultural center within the German federal system.
-
D.
independent city in Germany
An independent city in Germany is a municipality that holds the status of both a city and a district (kreisfreie Stadt), administering local and district-level responsibilities without being part of a surrounding rural district.
-
E.
district of Saxony
A district of Saxony is an administrative subdivision within the federal state of Saxony in Germany, responsible for local governance, public services, and regional planning across multiple municipalities.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:20 p.m.