Triple
T30025372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niederjosbach |
E762866
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Eppstein |
C56650
|
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 Eppstein Context triple: [Niederjosbach, instanceOf, district of Eppstein]
-
A.
district of Dillenburg
The district of Dillenburg is an administrative division centered around the town of Dillenburg, encompassing surrounding communities for local governance and regional organization.
-
B.
district of Brackenheim
The district of Brackenheim is an administrative subdivision centered around the town of Brackenheim, encompassing its surrounding settlements, governance structures, and local services within a defined geographic area.
-
C.
district of Weil am Rhein
A district of Weil am Rhein is an administrative subdivision of the town that encompasses specific residential, commercial, and infrastructural areas within its municipal boundaries.
-
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 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.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:48 p.m.