Triple
T16984042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angus Douglas-Hamilton, 15th Duke of Hamilton |
E412016
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Brandon |
C38357
|
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 Brandon Context triple: [Angus Douglas-Hamilton, 15th Duke of Hamilton, instanceOf, Duke of Brandon]
-
A.
Duke of Penthièvre
The Duke of Penthièvre is a French noble title historically associated with a high-ranking peer of France, often linked to the House of Bourbon and significant territorial and political influence in Brittany.
-
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 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.
-
D.
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.
-
E.
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.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:32 a.m.