Triple
T30749347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Sandwich |
E782910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | earldom in the peerage of England |
C51767
|
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 England Context triple: [Earl of Sandwich, instanceOf, earldom in the peerage of England]
-
A.
earldom in the Peerage of England
chosen
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.
-
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.
Earl in the Peerage of Ireland
An Earl in the Peerage of Ireland is a noble title ranking below a marquess and above a viscount within the historical Irish system of hereditary peerage, often associated with specific territorial designations and privileges.
-
D.
Earl of Shrewsbury
The Earl of Shrewsbury is a hereditary English noble title in the Peerage of England, historically associated with significant political influence, military leadership, and extensive landholdings, particularly in the Shropshire region.
-
E.
Earl of Bedford
The Earl of Bedford is a hereditary noble title in the Peerage of England historically associated with the Russell family, who have played significant political and social roles in British 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:38 p.m.