Triple
T28818868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reinsberg |
E727704
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local municipality in Germany |
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: local municipality in Germany Context triple: [Reinsberg, instanceOf, local municipality in Germany]
-
A.
rural municipality in Germany
A rural municipality in Germany is a local administrative unit, typically comprising smaller towns and villages, that manages local governance, infrastructure, and community services within a predominantly non-urban area.
-
B.
town in Germany
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.
-
C.
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.
-
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.
rural district of Germany
A rural district of Germany is an administrative subdivision, typically encompassing several towns and municipalities, that manages regional services such as infrastructure, education, and public welfare in predominantly non-urban areas.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:33 a.m.