Triple
T9511017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Henry, Duke of Gloucester and Edinburgh |
E229393
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Gloucester and Edinburgh |
C26377
|
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 Gloucester and Edinburgh Context triple: [William Henry, Duke of Gloucester and Edinburgh, instanceOf, Duke of Gloucester and Edinburgh]
-
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 York
The Duke of York is a noble title in the British peerage traditionally granted to the second son of the reigning monarch, historically associated with significant political and military influence.
-
C.
Duke of Richmond
The Duke of Richmond is a hereditary noble title in the Peerage of England, historically granted to members of the royal family or high-ranking aristocrats associated with the region of Richmond.
-
D.
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.
-
E.
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.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 7:58 p.m.