Triple
T9272744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dál gCais |
E222870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval ruling kindred |
C3349
|
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 ruling kindred Context triple: [Dál gCais, instanceOf, medieval ruling kindred]
-
A.
group of medieval polities
A group of medieval polities is a collection of semi-autonomous kingdoms, principalities, city-states, or other territorial entities that interacted through shifting alliances, conflicts, and hierarchies within the broader sociopolitical landscape of the Middle Ages.
-
B.
medieval nobility
chosen
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.
-
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.
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.
-
E.
late medieval ruler
A late medieval ruler is a sovereign who governed a kingdom or principality in Europe roughly between the 13th and 15th centuries, navigating feudal structures, emerging centralized authority, and complex dynastic, religious, and military conflicts.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:33 p.m.