Triple
T6425863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Murray, 2nd Duke of Atholl |
E128056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke in the Peerage of Scotland |
C3486
|
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 in the Peerage of Scotland Context triple: [James Murray, 2nd Duke of Atholl, instanceOf, Duke in the Peerage of Scotland]
-
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.
Scottish earldom
A Scottish earldom is a hereditary noble title in the peerage of Scotland, historically granting its holder territorial authority, social precedence, and certain feudal or ceremonial privileges within the Scottish realm.
-
C.
High Steward of Scotland
The High Steward of Scotland was a hereditary noble office responsible for managing the royal household and estates, which evolved into the dynastic title held by the Stewart (later Stuart) family who became kings of Scotland and England.
-
D.
Scottish nobleman
chosen
A Scottish nobleman is a male member of the Scottish aristocracy who holds a hereditary or granted title, land, and social status within Scotland’s traditional feudal hierarchy.
-
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.
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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:43 p.m.