Triple
T3003418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown of Aragon |
E81841
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval composite monarchy |
C2643
|
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 composite monarchy Context triple: [Crown of Aragon, instanceOf, medieval composite monarchy]
-
A.
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.
-
B.
composite monarchy
chosen
A composite monarchy is a form of rule in which a single monarch governs multiple distinct territories or states, each retaining its own laws, institutions, and customs under a shared crown.
-
C.
medieval parliament
A medieval parliament is an assembly of nobles, clergy, and sometimes commoners convened by a monarch to advise on governance, consent to taxation, and address matters of law and policy.
-
D.
medieval duchy
A medieval duchy is a territorial domain ruled by a duke or duchess, typically semi-autonomous within a larger kingdom or empire, with its own feudal hierarchy, laws, and military obligations.
-
E.
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.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:59 p.m.