Triple
T4472318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crusader states |
E98522
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of medieval polities |
C15860
|
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: group of medieval polities Context triple: [Crusader states, instanceOf, group of medieval polities]
-
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.
historic confederation of towns
A historic confederation of towns is a formal alliance of multiple municipalities that cooperatively coordinate defense, trade, governance, or mutual support while retaining their individual local autonomy.
-
C.
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.
-
D.
Iberian polity
An Iberian polity is a political entity—such as a kingdom, state, or autonomous region—located on or historically associated with the Iberian Peninsula, encompassing parts of modern Spain, Portugal, Andorra, Gibraltar, and adjacent territories.
-
E.
early medieval kingdom
An early medieval kingdom is a territorially bounded, monarch-led polity emerging after the fall of the Western Roman Empire, characterized by decentralized power, personal lordship ties, and a fusion of Roman, Germanic, and Christian traditions.
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:35 p.m.