Triple
T29006761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Lloyd of Berwick |
E736456
|
entity |
| Predicate | retiredAsLordOfAppealInOrdinary |
P82658
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Lord Lloyd of Berwick, retiredAsLordOfAppealInOrdinary, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredAsLordOfAppealInOrdinary Context triple: [Lord Lloyd of Berwick, retiredAsLordOfAppealInOrdinary, 1998]
-
A.
retiredAsLawLord
chosen
Indicates that a person ended their judicial career while serving in the position of Law Lord.
-
B.
appointedAsLordOfAppealInOrdinary
Indicates that a person has been formally appointed to serve in the judicial office of Lord of Appeal in Ordinary.
-
C.
appointedLordOfAppealInOrdinaryYear
Indicates the year in which an individual was appointed as a Lord of Appeal in Ordinary.
-
D.
retiredFromHouseOfLordsJudicialCommitteeYear
Indicates the year in which an individual ceased serving on the House of Lords Judicial Committee.
-
E.
retirementFromHouseOfLordsJudicialCommittee
Indicates that an individual has ceased serving as a member of the House of Lords Judicial Committee.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fc08c78819086abfcb2c02af163 |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:38 a.m.