Triple
T31344041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marburg-Biedenkopf |
E799390
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Hesse |
C59666
|
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: district of Hesse Context triple: [Marburg-Biedenkopf, instanceOf, district of Hesse]
-
A.
district of Ludwigshafen am Rhein
A district of Ludwigshafen am Rhein is an administrative subdivision of the city that encompasses specific residential, commercial, and infrastructural areas governed under the municipal authority of Ludwigshafen am Rhein, Germany.
-
B.
district of Mainz
A district of Mainz is an administrative subdivision of the city of Mainz, Germany, encompassing specific neighborhoods and local governance functions within the urban area.
-
C.
district of North Rhine-Westphalia
A district of North Rhine-Westphalia is an administrative territorial unit within the German federal state of North Rhine-Westphalia, responsible for regional governance, public services, and local coordination among its municipalities.
-
D.
district of Karlsruhe
A district of Karlsruhe is an administrative subdivision within the city or surrounding region of Karlsruhe, responsible for local governance, services, and community organization in its designated area.
-
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. 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:17 p.m.