Triple
T8001403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President of the King’s Bench Division |
E186255
|
entity |
| Predicate | statutoryRetirementAge |
P2272
|
FINISHED |
| Object | 70 years |
—
|
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: 70 years | Statement: [President of the King’s Bench Division, statutoryRetirementAge, 70 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statutoryRetirementAge Context triple: [President of the King’s Bench Division, statutoryRetirementAge, 70 years]
-
A.
mandatoryRetirementAge
chosen
Indicates the age at which an individual is required by rule or policy to retire from a position or role.
-
B.
retirementYear
Indicates the specific year in which an entity retires or is officially considered retired.
-
C.
earliestRetirementPensionStartAge
Indicates the minimum age at which an individual is first allowed to begin receiving retirement pension benefits.
-
D.
retirementPeriod
Indicates the time span during which an entity is considered to be retired or in retirement status.
-
E.
latestRetirementPensionStartAge
Indicates the most recent or maximum age at which an individual’s retirement pension payments are scheduled to begin.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c9cd06081908b62bb41e228c321 |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:18 p.m.