Triple
T17275549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siemens S200 |
E419381
|
entity |
| Predicate | replacesRollingStockType |
P84259
|
FINISHED |
| Object | older high-floor LRVs |
—
|
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 high-floor LRVs | Statement: [Siemens S200, replacesRollingStockType, older high-floor LRVs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesRollingStockType Context triple: [Siemens S200, replacesRollingStockType, older high-floor LRVs]
-
A.
replacedRollingStock
Indicates that one rolling stock asset has been substituted or superseded by another in service or operational use.
-
B.
successorRollingStockType
chosen
Indicates that one rolling stock type directly follows and replaces another in operational succession.
-
C.
formerRollingStock
Indicates that an entity was previously used as rolling stock (e.g., railway vehicles) but no longer serves in that capacity.
-
D.
rollingStockType
Indicates the specific category or type of railway rolling stock associated with an entity (e.g., locomotive, passenger car, freight wagon).
-
E.
relatedRollingStock
Indicates a relationship between pieces of rolling stock that are associated with each other, such as through shared operations, configurations, or functional linkage.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4332625c48190a25bf51543d797c3 |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.