Triple
T18248376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Line (selected runs over time) |
E437013
|
entity |
| Predicate | rollingStockSeries |
P45556
|
FINISHED |
| Object | 5000-series |
—
|
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: 5000-series | Statement: [Blue Line (selected runs over time), rollingStockSeries, 5000-series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rollingStockSeries Context triple: [Blue Line (selected runs over time), rollingStockSeries, 5000-series]
-
A.
rollingStockType
Indicates the specific category or type of railway rolling stock associated with an entity (e.g., locomotive, passenger car, freight wagon).
-
B.
rollingStockFamily
chosen
Indicates a relationship where a piece of rolling stock belongs to, or is classified under, a particular family or series of related rolling stock designs.
-
C.
rollingStockEra
Indicates the historical or operational time period during which a particular piece of rolling stock is designed to represent or is considered appropriate.
-
D.
rollingStockLength
Indicates the length measurement of a piece of rolling stock in a rail or transit system.
-
E.
rollingStockGauge
Indicates that one rolling stock entity is designed to operate on tracks built to a specific track gauge standard.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e89b288190a286797ec2cd60a8 |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:33 a.m.