Triple
T37203018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumo (Class 803 variant) |
E922091
|
entity |
| Predicate | rollingStockPowerConfiguration |
P187660
|
FINISHED |
| Object | pure electric |
—
|
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: pure electric | Statement: [Lumo (Class 803 variant), rollingStockPowerConfiguration, pure electric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rollingStockPowerConfiguration Context triple: [Lumo (Class 803 variant), rollingStockPowerConfiguration, pure electric]
-
A.
rollingStockPowerType
chosen
Indicates the type of propulsion or power system used by a piece of rolling stock.
-
B.
rollingStockPowerSupply
Indicates that one rolling stock entity provides or is associated with a specific power supply used to operate or support another entity.
-
C.
locomotiveConfiguration
Indicates the specific arrangement and type of power and running units (e.g., wheel or axle layout) that define how a locomotive is configured.
-
D.
rollingStockType
Indicates the specific category or type of railway rolling stock associated with an entity (e.g., locomotive, passenger car, freight wagon).
-
E.
rollingStockRole
Indicates the functional role or purpose that a piece of rolling stock serves within a railway system.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:15 p.m.