Triple
T15696737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lordship of Annandale |
E380481
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval territorial lordship |
C6478
|
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 territorial lordship Context triple: [Lordship of Annandale, instanceOf, medieval territorial lordship]
-
A.
territorial lordship
chosen
Territorial lordship is a system of authority in which a lord exercises political, legal, and economic control over a defined geographic area and its inhabitants, typically by hereditary or feudal right.
-
B.
feudal territories
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.
medieval nobility
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.
-
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.
medieval political status
Medieval political status refers to the hierarchical position and associated rights, duties, and privileges of individuals or groups within the feudal and monarchical power structures of the Middle Ages.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:44 a.m.