Triple
T29006762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Lloyd of Berwick |
E736456
|
entity |
| Predicate | appointedAsLordJusticeOfAppeal |
P82654
|
FINISHED |
| Object | 1984 |
—
|
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: 1984 | Statement: [Lord Lloyd of Berwick, appointedAsLordJusticeOfAppeal, 1984]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsLordJusticeOfAppeal Context triple: [Lord Lloyd of Berwick, appointedAsLordJusticeOfAppeal, 1984]
-
A.
appointedAsLordOfAppealInOrdinary
Indicates that a person has been formally appointed to serve in the judicial office of Lord of Appeal in Ordinary.
-
B.
appointedAsLawLord
Indicates that an individual has been formally appointed to serve as a Law Lord (a judicial member of the House of Lords).
-
C.
appointedLordOfAppealInOrdinaryYear
Indicates the year in which an individual was appointed as a Lord of Appeal in Ordinary.
-
D.
appointedLordJusticeOfAppealYear
chosen
Indicates the year in which a person was appointed to the position of Lord Justice of Appeal.
-
E.
appointedAsJusticeOfSupremeCourt
Indicates that an entity has been formally selected and installed to serve as a justice 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 9:38 a.m.