Triple
T26203529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonathan Hugh Mance |
E655297
|
entity |
| Predicate | retiredFromSupremeCourt |
P85095
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Jonathan Hugh Mance, retiredFromSupremeCourt, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromSupremeCourt Context triple: [Jonathan Hugh Mance, retiredFromSupremeCourt, 2018]
-
A.
servedOnSupremeCourtUntil
chosen
Indicates that an individual held a position on the Supreme Court up to and including a specified end date.
-
B.
retiredAsLawLord
Indicates that a person ended their judicial career while serving in the position of Law Lord.
-
C.
succeededInSupremeCourtSeatBy
Indicates that one individual directly followed another in occupying the same seat on the Supreme Court.
-
D.
succeededInOfficeAsAssociateJusticeBy
Indicates that one associate justice left office and was subsequently replaced in that judicial position by another associate justice.
-
E.
nominatedToSupremeCourtBy
Indicates that one entity formally selected or put forward another entity as a candidate for a position on the Supreme Court.
- F. None of above.
Provenance (3 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cdd664c8190862fe9543ab251c9 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:49 p.m.