Triple
T24359532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 57 |
E614016
|
entity |
| Predicate | rebuildPeriodEnd |
P155915
|
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, rebuildPeriodEnd, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuildPeriodEnd Context triple: [British Rail Class 57, rebuildPeriodEnd, 2004]
-
A.
rebuildPeriod
Indicates the time span during which something is reconstructed or restored after damage, failure, or decommissioning.
-
B.
buildPeriodEnd
Indicates the point in time at which a construction or building phase is considered completed.
-
C.
rebuiltEnd
Indicates that one entity has been reconstructed, restored, or rebuilt at the endpoint or conclusion of another entity or process.
-
D.
focusPeriodEnd
Indicates the point in time at which a specified focus period or interval concludes.
-
E.
associatedPeriodEnd
Indicates the ending point or final date of the time period with which something is associated.
- F. None of above. chosen
Provenance (4 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2934bcc608190b86bc091474bb259 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2 a.m.