Triple
T21333673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Montgomery, 6th Earl of Eglinton |
E525978
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Earl of Eglinton |
C44692
|
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: Earl of Eglinton Context triple: [Alexander Montgomery, 6th Earl of Eglinton, instanceOf, Earl of Eglinton]
-
A.
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.
-
B.
Earl of Buchan
The Earl of Buchan is a Scottish noble title in the Peerage of Scotland historically associated with the Buchan region in northeast Scotland and held by various prominent families over the centuries.
-
C.
Earl of Carrick
The Earl of Carrick is a noble title historically associated with the Scottish earldom of Carrick in Ayrshire, often linked to significant medieval Scottish royalty and aristocracy.
-
D.
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.
-
E.
Earl of Northesk
The Earl of Northesk is a hereditary title in the Peerage of Scotland traditionally associated with the Carnegie family and historically linked to military and political service.
- 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_69e0b51b90788190a4dd823d962626da |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 4:43 p.m.