Triple
T29669433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Talbot, 16th Earl of Shrewsbury |
E750623
|
entity |
| Predicate | succeededAsEarlOfShrewsburyInYear |
P196319
|
FINISHED |
| Object | 1827 |
—
|
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: 1827 | Statement: [John Talbot, 16th Earl of Shrewsbury, succeededAsEarlOfShrewsburyInYear, 1827]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededAsEarlOfShrewsburyInYear Context triple: [John Talbot, 16th Earl of Shrewsbury, succeededAsEarlOfShrewsburyInYear, 1827]
-
A.
successorAsEarlOfPembroke
Indicates that one entity became the next holder of the title Earl of Pembroke after another entity.
-
B.
succeededAsEarlOfKildare
Indicates that one person took over the title and position of Earl of Kildare from another, becoming their successor in that earldom.
-
C.
successorAsEarl
Indicates that one person became the next holder of the title of Earl after another person.
-
D.
successorAsEarlOfHuntingdon
Indicates that one person became the next Earl of Huntingdon following another person in that title or office.
-
E.
successorAsEarlOfStrathearn
Indicates that one individual became the next Earl of Strathearn following another, succeeding them in that noble 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
| PDg | Predicate description generation | batch_69fe21afdc4c8190913ac4b55a9a5f52 |
completed | May 8, 2026, 5:47 p.m. |
Created at: April 28, 2026, 7:03 p.m.