Triple
T14826704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Liverpool |
E348593
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | earldom in the Peerage of Great Britain |
C672
|
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 Great Britain Context triple: [Earl of Liverpool, instanceOf, earldom in the Peerage of Great Britain]
-
A.
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.
-
B.
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.
-
C.
peerage title
chosen
A peerage title is a hereditary or life rank of nobility granted by a sovereign, conferring social status and often certain legal or ceremonial privileges within a hierarchical aristocratic system.
-
D.
Earl of Orrery
The Earl of Orrery is a noble title in the Peerage of Ireland historically associated with the Boyle family, notably linked to political influence and the development of the mechanical model of the solar system known as an orrery.
-
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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:51 a.m.