Triple
T8859143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landkreis Heidenheim |
E210840
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Landkreis in Deutschland |
C11185
|
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: Landkreis in Deutschland Context triple: [Landkreis Heidenheim, instanceOf, Landkreis in Deutschland]
-
A.
Landkreis in Brandenburg
A "Landkreis in Brandenburg" is an administrative district within the federal state of Brandenburg in Germany, responsible for regional self-government, public services, and local infrastructure across multiple municipalities.
-
B.
rural district of Germany
chosen
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.
-
C.
region of Germany
A region of Germany is a geographically and culturally distinct area within the country, often defined by historical boundaries, administrative divisions, or shared economic and social characteristics.
-
D.
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.
-
E.
administrative region of Germany
An administrative region of Germany is a territorial unit within a federal state (Land) that serves as an intermediate level of government for coordinating regional administration, planning, and public services.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:50 p.m.