Triple
T23764203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 08 |
E587330
|
entity |
| Predicate | overhaulsIncluded |
P28319
|
FINISHED |
| Object | mechanical refurbishment |
—
|
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: mechanical refurbishment | Statement: [British Rail Class 08, overhaulsIncluded, mechanical refurbishment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overhaulsIncluded Context triple: [British Rail Class 08, overhaulsIncluded, mechanical refurbishment]
-
A.
overturnsInEffect
Indicates that one action, decision, or rule reverses and nullifies the current effect or validity of another.
-
B.
hasReconstructionWork
chosen
Indicates that an entity is undergoing, has undergone, or is associated with reconstruction or restoration work.
-
C.
overlays
Indicates that one entity is placed on top of or superimposed over another, partially or completely covering it in the same spatial area.
-
D.
reissueIncludes
Indicates that a reissued version of something contains or incorporates the referenced item as part of that reissue.
-
E.
overrides
Indicates that one entity replaces, supersedes, or takes precedence over another in determining the outcome or applicable behavior.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdb4e9248190b64b063637b66702 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:14 p.m.