Triple
T25022741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 57 |
E626622
|
entity |
| Predicate | rebuildEndYear |
P214
|
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 57, rebuildEndYear, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuildEndYear Context triple: [British Rail Class 57, rebuildEndYear, 2004]
-
A.
rebuiltApproximateEndYear
Indicates that an entity was rebuilt, with the specified year representing an approximate (not exact) end date of the rebuilding process.
-
B.
rebuildPeriodEnd
Indicates the point in time when a rebuilding or reconstruction process is scheduled or expected to be completed.
-
C.
endYear
chosen
Indicates the year in which an event, state, or relationship comes to an end.
-
D.
cleanupEndYear
Indicates the year in which a cleanup or remediation activity is completed or officially ends.
-
E.
rebuiltEnd
Indicates that one entity has been reconstructed, restored, or rebuilt at the endpoint or conclusion of another entity or process.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:07 a.m.