Triple
T19335248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giessen district |
E483605
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rural district in Hesse |
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: rural district in Hesse Context triple: [Giessen district, instanceOf, rural district in Hesse]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
district of Mannheim
A district of Mannheim is an administrative subdivision of the city of Mannheim, Germany, characterized by its own local neighborhoods, infrastructure, and community services within the broader urban 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.
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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:33 p.m.