Triple
T13287511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Toulouse |
E316481
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | feudal principality |
C32175
|
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: feudal principality Context triple: [County of Toulouse, instanceOf, feudal principality]
-
A.
hereditary principality
A hereditary principality is a sovereign or semi-sovereign territory ruled by a prince whose authority and title are passed down through a family line, typically by primogeniture or other dynastic succession rules.
-
B.
feudal territories
chosen
Feudal territories are landholdings governed by lords who exercise political, economic, and judicial authority over the land and its inhabitants in exchange for loyalty and service within a hierarchical system.
-
C.
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.
-
D.
vassal state
A vassal state is a subordinate political entity that retains limited internal autonomy while owing allegiance, tribute, or military support to a more powerful sovereign state.
-
E.
feudatory ruler
A feudatory ruler is a subordinate sovereign who governs a territory and owes allegiance, tribute, and military support to a more powerful overlord or suzerain.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:27 p.m.