Triple
T1140377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 170 |
E23435
|
entity |
| Predicate | enteredServiceAsReplacementFor |
P26479
|
FINISHED |
| Object | older first-generation DMUs |
—
|
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: older first-generation DMUs | Statement: [British Rail Class 170, enteredServiceAsReplacementFor, older first-generation DMUs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredServiceAsReplacementFor Context triple: [British Rail Class 170, enteredServiceAsReplacementFor, older first-generation DMUs]
-
A.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
B.
enteredServiceWithUnit
Indicates that an entity began its period of service or active duty while assigned to a specified unit.
-
C.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
D.
replacedStation
Indicates that one station has taken the place of another station, typically succeeding it in function, service, or location.
-
E.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4b52d48190bec2e7ad1cc8efc0 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bddfa598819088690e1ab010ba0b |
completed | March 1, 2026, 10:29 p.m. |
Created at: March 1, 2026, 7:44 p.m.