Triple
T30002826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | district of Lübeck (historical region) |
E762216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative 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: administrative district of Prussia Context triple: [district of Lübeck (historical region), instanceOf, administrative district of Prussia]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
administrative district of East Germany
An administrative district of East Germany was a mid-level territorial unit (Bezirk) established by the German Democratic Republic to organize regional governance, planning, and administration between the central government and local municipalities.
-
E.
former Prussian city
A former Prussian city is an urban settlement that historically belonged to the Kingdom of Prussia or the later Prussian state but now lies within the borders of a different modern nation.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:42 p.m.