Triple
T35711560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Plantagenet Campbell Temple-Nugent-Brydges-Chandos-Grenville, 3rd Duke of Buckingham and Chandos |
E1031873
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British duke |
C65039
|
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: British duke Context triple: [Richard Plantagenet Campbell Temple-Nugent-Brydges-Chandos-Grenville, 3rd Duke of Buckingham and Chandos, instanceOf, British duke]
-
A.
British royal
A British royal is a member of the United Kingdom’s monarchy, typically born or married into the royal family, who embodies and represents national tradition, continuity, and ceremonial leadership.
-
B.
Duke of Cornwall
The Duke of Cornwall is a hereditary royal title in the United Kingdom traditionally held by the eldest living son of the reigning monarch, granting him income and responsibilities derived from the Duchy of Cornwall estate.
-
C.
King of Sussex
The King of Sussex is a conceptual monarchic figure representing the sovereign ruler of the historical or fictional region of Sussex, embodying its political authority, cultural identity, and territorial governance.
-
D.
Duke of Edinburgh
The Duke of Edinburgh is a noble title in the British peerage traditionally granted to a senior member of the royal family, historically associated with significant public service and ceremonial duties.
-
E.
Duke of Saxe-Coburg and Gotha
The Duke of Saxe-Coburg and Gotha is a hereditary noble title historically held by the sovereign or head of the ducal house that ruled the German duchy of Saxe-Coburg and Gotha.
- 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.