Triple
T21015429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry de Lacy, Baron of Pontefract |
E517660
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nobleman of the Kingdom of England |
C14120
|
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: nobleman of the Kingdom of England Context triple: [Henry de Lacy, Baron of Pontefract, instanceOf, nobleman of the Kingdom of England]
-
A.
14th-century English noble
A 14th-century English noble is a high-ranking member of the medieval English aristocracy who holds land from the king, exercises local political and military authority, and participates in courtly and feudal obligations within a rigidly hierarchical society.
-
B.
peer of the Kingdom of England
chosen
A peer of the Kingdom of England is a noble holding one of the hereditary or life dignities (duke, marquess, earl, viscount, or baron) that conferred membership in the English peerage and historically a seat in the House of Lords.
-
C.
Anglo-French nobleman
An Anglo-French nobleman is an aristocrat whose lineage, titles, or holdings span both English and French realms, embodying the intertwined political, cultural, and familial ties between the two nobilities.
-
D.
Welsh noble
A Welsh noble is a member of the traditional aristocracy of Wales, historically holding land, titles, and local authority within the Welsh social and political hierarchy.
-
E.
medieval European noble
A medieval European noble is a high-ranking member of the feudal aristocracy who holds land granted by a monarch in exchange for military service and governance over vassals and peasants.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 1:54 p.m.