Triple
T34361363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hechingen district |
E881882
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Prussia |
C56635
|
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 Prussia Context triple: [Hechingen district, instanceOf, district of Prussia]
-
A.
administrative district of Prussia
chosen
An administrative district of Prussia was a mid-level territorial unit governed by a district president, responsible for implementing state policies, overseeing local administration, and coordinating between the central Prussian government and lower-level municipalities.
-
B.
district of East Prussia
A district of East Prussia was an administrative subdivision of the former German province of East Prussia, responsible for local governance, justice, and public services within its defined territorial boundaries.
-
C.
province of Prussia
A province of Prussia was a major administrative territorial unit within the Kingdom (and later state) of Prussia, serving as a top-level regional division for governance, law, and administration.
-
D.
province of Prussia
A province of Prussia was a major administrative and territorial division within the Kingdom (and later Free State) of Prussia, functioning as a regional unit of government with its own local authorities under the broader Prussian state.
-
E.
district of Kaliningrad
A district of Kaliningrad is an administrative subdivision within the city of Kaliningrad, Russia, responsible for local governance, public services, and community infrastructure in its designated urban area.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:58 a.m.