Triple
T11723964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince William Henry, Duke of Clarence |
E278711
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Clarence and St Andrews |
C13624
|
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 Clarence and St Andrews Context triple: [Prince William Henry, Duke of Clarence, instanceOf, Duke of Clarence and St Andrews]
-
A.
Duke of Clarence and Avondale
The Duke of Clarence and Avondale is a former British royal dukedom created in the late 19th century for Prince Albert Victor, the eldest son of the Prince of Wales, combining two historic territorial designations within the United Kingdom’s peerage system.
-
B.
Duke of Clarence
chosen
The Duke of Clarence is a noble title in the British peerage historically granted to junior members of the royal family, often associated with the region of Clare in Suffolk.
-
C.
Duke of Somerset
The Duke of Somerset is a hereditary title in the Peerage of England traditionally held by a high-ranking noble associated with the royal House of Beaufort and later other prominent aristocratic families.
-
D.
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.
-
E.
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.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:41 p.m.