Triple
T24726937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lordship of Glamorgan |
E618179
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | marcher lordship |
C33140
|
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: marcher lordship Context triple: [Lordship of Glamorgan, instanceOf, marcher lordship]
-
A.
marcher lord
chosen
A marcher lord is a noble granted authority over a border territory, empowered with military and administrative autonomy to defend and govern frontier regions.
-
B.
medieval march
A medieval march is a border territory or frontier region of a kingdom or empire, governed by a margrave or similar official, established to defend against external threats and manage cross-border relations.
-
C.
territorial lordship
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.
-
D.
Lord Warden of the Marches
The Lord Warden of the Marches was a high-ranking royal official responsible for governing, defending, and administering justice in the turbulent border regions between England and Scotland (or Wales) during the late medieval and early modern periods.
-
E.
barony
A barony is a feudal territorial unit governed by a baron or baroness, typically comprising lands, settlements, and associated rights and obligations within a larger kingdom or realm.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
Created at: April 18, 2026, 3:59 a.m.