Triple
T11391682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breslau, Province of Silesia, Kingdom of Prussia, German Empire |
E269856
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former German city |
C5575
|
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: former German city Context triple: [Breslau, Province of Silesia, Kingdom of Prussia, German Empire, instanceOf, former German city]
-
A.
former Prussian city
chosen
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.
-
B.
former German name of a town
A former German name of a town is a historical place-name once used in the German language for a specific settlement, typically replaced after political, territorial, or cultural changes.
-
C.
independent city in Germany
An independent city in Germany is a municipality that holds the status of both a city and a district (kreisfreie Stadt), administering local and district-level responsibilities without being part of a surrounding rural district.
-
D.
town in Germany
A town in Germany is a moderately sized, legally defined urban municipality that serves as a local administrative, economic, and cultural center within the German federal system.
-
E.
capital of a German state
A capital of a German state is the primary city where the government institutions and administrative bodies of one of Germany’s federal states are located.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:34 p.m.