Triple
T38168511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barony of Monthermer |
E953217
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English barony |
C6373
|
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: English barony Context triple: [Barony of Monthermer, instanceOf, English barony]
-
A.
historic barony
A historic barony is a territorial and social unit once governed by a baron, typically recognized within a feudal or aristocratic system, that now holds primarily historical, cultural, or ceremonial significance.
-
B.
12th-century English baron
A 12th-century English baron was a powerful landholding noble who held estates directly from the king in exchange for military and political service, exercising local authority over justice, taxation, and defense within the feudal system.
-
C.
barony
chosen
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.
-
D.
13th-century English noble
A 13th-century English noble is a high-ranking landowning aristocrat who wields military, judicial, and political power under the feudal monarchy, owing loyalty to the king while exercising authority over vassals and estates.
-
E.
Anglo-Breton noble
An Anglo-Breton noble is a medieval aristocrat of mixed English and Breton heritage who held land, titles, and political influence across both regions, often serving as a cultural and military intermediary between them.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.