Triple
T578992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamic Spain |
E15017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval polity |
C4114
|
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: medieval polity Context triple: [Islamic Spain, instanceOf, medieval polity]
-
A.
early modern polity
An early modern polity is a territorially bounded, politically organized community between roughly 1500 and 1800 that exercised authority through evolving institutions of governance, law, and sovereignty amid processes of state formation and imperial expansion.
-
B.
early modern Indian polity
Early modern Indian polity refers to the complex, regionally diverse systems of governance, authority, and political negotiation that emerged in the Indian subcontinent roughly between the 16th and 18th centuries, encompassing empires, kingdoms, and local powers interacting through warfare, diplomacy, and administration.
-
C.
medieval nobility
Medieval nobility comprised the hereditary warrior-elite who held land from a monarch in exchange for military and political service, dominating social, economic, and legal life in feudal Europe.
-
D.
early modern state
An early modern state is a centralized political entity that emerged in Europe between the 15th and 18th centuries, characterized by growing bureaucratic administration, territorial sovereignty, standing armies, and increasingly standardized systems of law and taxation.
-
E.
medieval county
A medieval county is a territorial and administrative unit governed by a count or similar noble, encompassing lands, settlements, and jurisdictions within a feudal hierarchy.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:33 p.m.