Triple
T30773639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Dalkeith |
E783597
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | earldom in the Peerage of Scotland |
C673
|
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: earldom in the Peerage of Scotland Context triple: [Earl of Dalkeith, instanceOf, earldom in the Peerage of Scotland]
-
A.
Scottish earldom
chosen
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.
-
B.
earldom in the Peerage of England
An earldom in the Peerage of England is a hereditary noble title of earl rank, created by the English Crown and forming part of the traditional hierarchy of English nobility below marquess and above viscount.
-
C.
Earl of Fife
The Earl of Fife is a Scottish noble title historically associated with the powerful MacDuff family, traditionally holding significant regional authority and prestige in the Kingdom of Scotland.
-
D.
Earl of Eglinton
The Earl of Eglinton is a hereditary title in the Peerage of Scotland historically associated with the Montgomerie family and centered on Eglinton Castle in Ayrshire.
-
E.
Earl of Atholl
The Earl of Atholl is a Scottish noble title historically associated with the Atholl region in the central Highlands, held by various prominent families and often linked to significant political and military roles in Scotland’s history.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:40 p.m.