Triple
T33451887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry John Montagu Douglas Scott, 1st Duke of Buccleuch |
E856666
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Buccleuch |
C58920
|
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 Buccleuch Context triple: [Henry John Montagu Douglas Scott, 1st Duke of Buccleuch, instanceOf, Duke of Buccleuch]
-
A.
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.
-
B.
Duke of Argyll
The Duke of Argyll is a hereditary Scottish noble title historically held by the chief of Clan Campbell, traditionally associated with significant political influence, military leadership, and extensive landholdings in Argyll, Scotland.
-
C.
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.
-
D.
Earl of Strathmore and Kinghorne
The Earl of Strathmore and Kinghorne is a hereditary Scottish peerage title in the Peerage of Scotland, historically associated with the Lyon family and Glamis Castle, and notable for its close connections to the British royal family.
-
E.
Duke of Atholl
The Duke of Atholl is a hereditary Scottish peerage title historically associated with the Murray family, notable for its extensive Highland estates and unique privilege of maintaining a private army, the Atholl Highlanders.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:37 a.m.