Triple
T38215462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Apulia |
E1010672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norman principality |
C65236
|
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: Norman principality Context triple: [County of Apulia, instanceOf, Norman principality]
-
A.
medieval Welsh principality
A medieval Welsh principality is a semi-independent territorial lordship in Wales, ruled by a native prince who exercised political, military, and legal authority within a feudal landscape dominated by competing Welsh dynasties and encroaching English power.
-
B.
Piast-ruled principality
A Piast-ruled principality is a medieval territorial polity in Central Europe governed by a member of the Piast dynasty, typically characterized by fragmented authority, hereditary rule, and integration into the broader political landscape of the Polish and neighboring realms.
-
C.
Catalan principality
A Catalan principality is a medieval or early modern political entity in which Catalan-speaking territories were governed by a prince or similar sovereign authority, often within larger composite monarchies.
-
D.
Turkish principality
A Turkish principality is a semi-independent, territorially defined political entity ruled by a Turkish dynastic leader, typically emerging in the medieval or early modern period within the broader context of Turkic state formation and regional power dynamics.
-
E.
Norman ruler
A Norman ruler is a sovereign or feudal lord of Norman origin who exercises political and military authority over a territory, often characterized by a blend of Viking heritage and Frankish culture.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.