Triple
T12371072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John of Brittany, Earl of Richmond |
E295001
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Earl of Richmond |
C31366
|
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 Richmond Context triple: [John of Brittany, Earl of Richmond, instanceOf, Earl of Richmond]
-
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.
Duke of Lancaster
The Duke of Lancaster is a noble title in the Peerage of England historically associated with the ruling monarch and the administration of the Duchy of Lancaster, a royal estate providing independent income to the sovereign.
-
C.
Duke of Northumberland
The Duke of Northumberland is a hereditary noble title in the Peerage of Great Britain traditionally held by the head of the Percy family, historically one of the most powerful aristocratic dynasties in northern England.
-
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 Kent
The Earl of Kent is a noble title in the English peerage historically granted to powerful aristocrats who governed the county of Kent and held significant political and social influence.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:54 p.m.