Triple
T25022740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 57 |
E626622
|
entity |
| Predicate | rebuildStartYear |
P23768
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [British Rail Class 57, rebuildStartYear, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuildStartYear Context triple: [British Rail Class 57, rebuildStartYear, 1997]
-
A.
constructionResumptionYear
Indicates the year in which a previously halted or paused construction activity was resumed.
-
B.
rebuiltApproximateEndYear
Indicates that an entity was rebuilt, with the specified year representing an approximate (not exact) end date of the rebuilding process.
-
C.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
D.
reconstructionStartYear
chosen
Indicates the calendar year in which a reconstruction process or project began.
-
E.
rebuildingCycleYears
Indicates the number of years that typically pass between successive rebuilding or reconstruction cycles of something.
- 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_69f44f672d50819094261f5522c939e4 |
completed | May 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:07 a.m.