Triple
T34756206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Quito |
E1001930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | contested historical polity |
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: contested historical polity Context triple: [Kingdom of Quito, instanceOf, contested historical polity]
-
A.
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.
-
B.
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.
-
C.
medieval polity
A medieval polity is a territorially based political entity of the Middle Ages—such as a kingdom, duchy, city-state, or principality—defined by overlapping authorities, personal allegiances, and often fragmented sovereignty rather than a centralized nation-state structure.
-
D.
political history
Political history is the study of how power, governance, institutions, leaders, and political movements have developed and interacted over time to shape societies and states.
-
E.
historical policy
Historical policy is a conceptual class encompassing formal rules, laws, and governance decisions implemented in the past that shaped societal, economic, and political developments over time.
- 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.