Triple
T25022750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 57 |
E626622
|
entity |
| Predicate | rebuildMethod |
P30323
|
FINISHED |
| Object | re-engined with EMD power units |
—
|
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: re-engined with EMD power units | Statement: [British Rail Class 57, rebuildMethod, re-engined with EMD power units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuildMethod Context triple: [British Rail Class 57, rebuildMethod, re-engined with EMD power units]
-
A.
rebuild
Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
-
B.
rebuildType
Indicates the type or category of rebuilding or reconstruction process applied to an entity.
-
C.
rebuildingPattern
Indicates a recurring process in which something previously damaged, lost, or dismantled is systematically restored or reconstructed.
-
D.
reconstructionMethod
chosen
Indicates the technique or process used to reconstruct, restore, or rebuild something from its original or fragmented state.
-
E.
relocationMethod
Indicates the means or process by which something or someone is moved from one location to another.
- 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_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:07 a.m.