Triple
T3353325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmund of Langley, 1st Duke of York |
E70546
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of York |
C12636
|
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: Duke of York Context triple: [Edmund of Langley, 1st Duke of York, instanceOf, Duke of York]
-
A.
Duke of Gloucester
The Duke of Gloucester is a noble title in the British peerage traditionally granted to junior members of the royal family, historically associated with high status, military service, and close proximity to the monarch.
-
B.
Duke of Kent
The Duke of Kent is a hereditary noble title in the British peerage traditionally granted to a close male relative of the reigning monarch, historically associated with high social rank, landholdings, and ceremonial duties.
-
C.
Duke of Lancaster
The Duke of Lancaster is a noble title in the Peerage of England historically associated with the ruling monarch and the administration of the Duchy of Lancaster, a royal estate providing independent income to the sovereign.
-
D.
Duke of Fife
The Duke of Fife is a hereditary title in the Peerage of the United Kingdom, traditionally associated with the Fife region of Scotland and historically granted to members of the British royal family or their close relatives.
-
E.
Duke of Sussex
The Duke of Sussex is a hereditary or granted noble title in the British peerage, historically associated with members of the royal family and denoting high aristocratic rank and status.
- F. None of above. chosen
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_69ad85a4ef7c8190a29e2bbd6fa454e4 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:13 p.m.