Triple
T25568469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | law lord |
E640903
|
entity |
| Predicate | endOfPrimaryJudicialRole |
P41368
|
FINISHED |
| Object | 1 October 2009 |
—
|
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: 1 October 2009 | Statement: [law lord, endOfPrimaryJudicialRole, 1 October 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfPrimaryJudicialRole Context triple: [law lord, endOfPrimaryJudicialRole, 1 October 2009]
-
A.
judicialRole
Indicates that one entity holds or performs a specific official function or position within the judicial system in relation to another entity or legal matter.
-
B.
finalPeriodRole
Indicates the role or function an entity holds during the final period or concluding phase of a specified interval or process.
-
C.
endOfTenure
chosen
Indicates the point or event at which an entity’s period of holding a role, position, or office concludes.
-
D.
hasPrincipalJudge
Indicates that one entity serves as the main or presiding judge for another entity, such as a court or judicial body.
-
E.
laterPrimaryRole
Indicates that an entity assumes a specified primary role at a later time than another role or state in a sequence.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8fe0abc8190862167a5d282e107 |
completed | May 2, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 3:50 p.m.