Triple
T24131176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Henry, Duke of Cumberland and Strathearn |
E597956
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Cumberland and Strathearn |
C48297
|
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 Cumberland and Strathearn Context triple: [Prince Henry, Duke of Cumberland and Strathearn, instanceOf, Duke of Cumberland and Strathearn]
-
A.
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.
-
B.
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.
-
C.
Duke of Lennox
The Duke of Lennox is a noble title in the Peerage of Scotland historically granted to members of the royal Stuart (Stewart) family, often associated with high status, landholdings, and influence near the Scottish court.
-
D.
Duke of Hamilton
The Duke of Hamilton is a hereditary Scottish noble title, traditionally held by the head of the Hamilton family and recognized as one of the premier peerages in the Scottish nobility.
-
E.
Duke of Gloucester and Edinburgh
The Duke of Gloucester and Edinburgh is a historical British peerage title traditionally granted to a royal prince, combining associations with the English city of Gloucester and the Scottish capital of Edinburgh.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:25 p.m.