Triple
T10690256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Montagu, 1st Earl of Salisbury |
E251991
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Earl of Salisbury |
C28627
|
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 Salisbury Context triple: [William Montagu, 1st Earl of Salisbury, instanceOf, Earl of Salisbury]
-
A.
Earl of Pembroke
The Earl of Pembroke is a noble title in the Peerage of England historically granted to powerful magnates who held significant political, military, and territorial influence, particularly in Wales and along the English–Welsh border.
-
B.
Earl of Leicester
The Earl of Leicester is a noble title in the Peerage of England historically granted to prominent aristocrats who held significant political, military, and social influence, particularly during the medieval and early modern periods.
-
C.
Earl of Lancaster
The Earl of Lancaster was a prominent English noble title, often held by close relatives of the king, associated with extensive lands, political influence, and a key role in medieval English governance and conflicts.
-
D.
Duke of Somerset
The Duke of Somerset is a hereditary title in the Peerage of England traditionally held by a high-ranking noble associated with the royal House of Beaufort and later other prominent aristocratic families.
-
E.
Earl of Derby
The Earl of Derby is a hereditary title in the Peerage of England, historically associated with the influential Stanley family, whose holders have played prominent political and social roles since the late Middle Ages.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:11 p.m.