Triple
T35951174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial City of Dinkelsbühl |
E1039729
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former imperial free city |
C66298
|
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 imperial free city Context triple: [Imperial City of Dinkelsbühl, instanceOf, former imperial free city]
-
A.
former Free Imperial City
chosen
A former Free Imperial City is a town or city that once held the status of being directly subject to the Holy Roman Emperor, enjoying considerable self-governance and autonomy, but later lost this status through mediatisation, annexation, or political reorganization.
-
B.
former Hanseatic town
A former Hanseatic town is a city that was once a member of the medieval Hanseatic League, historically engaged in extensive maritime trade and governed by shared commercial and legal frameworks.
-
C.
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.
-
D.
former independent city
A former independent city is an urban settlement that once possessed its own municipal government and administrative autonomy but has since been incorporated into a larger city or governing entity.
-
E.
administrative district of the Holy Roman Empire
An administrative district of the Holy Roman Empire was a territorial unit governed by imperial or local authorities to organize political, judicial, and fiscal control within the Empire’s decentralized structure.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.