Triple
T25016358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 56 |
E626142
|
entity |
| Predicate | retiredFromBRMainline |
P81993
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [British Rail Class 56, retiredFromBRMainline, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromBRMainline Context triple: [British Rail Class 56, retiredFromBRMainline, 2004]
-
A.
retiredFromBRService
chosen
Indicates that an entity has ceased active service or operation within the British Rail (BR) system.
-
B.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
C.
retiredBy
Indicates that one entity has formally ended the active status, use, or service of another entity.
-
D.
retiredAsPlayerFrom
Indicates that an individual ended their professional playing career while being associated with a specific team, organization, or context.
-
E.
isRetiredAsPlayer
Indicates that an individual has ended their active career or participation in a sport or game as a player.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:06 a.m.