Triple
T2390869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon de Montfort, 6th Earl of Leicester |
E48938
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Earl of Leicester |
C11521
|
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 Leicester Context triple: [Simon de Montfort, 6th Earl of Leicester, instanceOf, Earl of Leicester]
-
A.
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.
-
B.
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.
-
C.
Earl of Oxford and Asquith
Earl of Oxford and Asquith is a British hereditary peerage title in the United Kingdom, created in 1925 for former Prime Minister H. H. Asquith, combining the historic earldom of Oxford with his family name.
-
D.
Earl of Cork
The Earl of Cork is a hereditary noble title in the Peerage of Ireland, historically associated with the Boyle family and centered around County Cork.
-
E.
Duke of Marlborough
The Duke of Marlborough is a hereditary British noble title in the Peerage of England, created in 1702 for the military commander John Churchill in recognition of his victories during the War of the Spanish Succession.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:57 p.m.