Triple
T14167716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stuttgart-Urach |
E351123
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical political arrangement |
C24030
|
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: historical political arrangement Context triple: [Stuttgart-Urach, instanceOf, historical political arrangement]
-
A.
historical political system
A historical political system is an organized structure of governance, power relations, and institutions that operated within a specific society and time period, shaping how authority was distributed, exercised, and justified.
-
B.
colonial political organization
A colonial political organization is a governing structure imposed by a foreign power to administer, control, and exploit a colonized territory and its population, often subordinating local institutions and interests to imperial objectives.
-
C.
former political institution
A former political institution is an organization or governing body that once held official political authority or administrative power but has since been dissolved, replaced, or rendered inactive.
-
D.
historical alliance
A historical alliance is a formal or informal partnership between states, groups, or leaders formed in the past to pursue shared political, military, economic, or cultural goals.
-
E.
historical polities
chosen
Historical polities are organized political entities or governing structures that existed in the past, such as kingdoms, empires, city-states, and federations, defined by their territorial control, institutions, and sociopolitical systems.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1 a.m.