Triple
T30850517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilmot Vaughan, 1st Earl of Lisburne |
E785765
|
entity |
| Predicate | succeededToViscountcyInYear |
P197877
|
FINISHED |
| Object | 1766 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1766 | Statement: [Wilmot Vaughan, 1st Earl of Lisburne, succeededToViscountcyInYear, 1766]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededToViscountcyInYear Context triple: [Wilmot Vaughan, 1st Earl of Lisburne, succeededToViscountcyInYear, 1766]
-
A.
successorAsEarl
Indicates that one person became the next holder of the title of Earl after another person.
-
B.
succeededAsEarlOfShrewsburyInYear
Indicates that one person became the Earl of Shrewsbury in a specified year, directly following another person in that title.
-
C.
createdViscount
Indicates that one entity granted or established the noble title of viscount for another entity.
-
D.
dateOfElevationToPeerage
Indicates the specific date on which an individual was formally elevated to a rank of nobility or peerage.
-
E.
succeededByInMarquessate
Indicates that one entity was the immediate successor of another in holding a particular marquessate title.
- F. None of above. chosen
Provenance (4 batches)
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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
| PDg | Predicate description generation | batch_69feb5e50a7481908d6bff55bd85e06d |
completed | May 9, 2026, 4:19 a.m. |
Created at: April 29, 2026, 8:46 p.m.