Triple
T1715738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roger de Montgomery |
E37285
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norman nobleman |
C1905
|
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: Norman nobleman Context triple: [Roger de Montgomery, instanceOf, Norman nobleman]
-
A.
Norman ruler
A Norman ruler is a sovereign or feudal lord of Norman origin who exercises political and military authority over a territory, often characterized by a blend of Viking heritage and Frankish culture.
-
B.
Scottish nobleman
A Scottish nobleman is a male member of the Scottish aristocracy who holds a hereditary or granted title, land, and social status within Scotland’s traditional feudal hierarchy.
-
C.
nobleman
chosen
A nobleman is a male member of the aristocracy who holds a hereditary or granted title, social privileges, and often land or political influence within a hierarchical society.
-
D.
Scottish knight
A Scottish knight is a medieval mounted warrior of Scottish origin, bound by chivalric codes and feudal allegiance, distinguished by regional arms, armor, and participation in Scotland’s historic conflicts.
-
E.
Duke of Normandy
The Duke of Normandy was a medieval noble title denoting the sovereign or semi-sovereign ruler of the Duchy of Normandy, a powerful feudal territory in northwestern France that played a pivotal role in European politics, especially after its dukes became kings of England.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.