Triple
T6335743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S25 |
E142485
|
entity |
| Predicate | rollingStockPowerSupply |
P70927
|
FINISHED |
| Object | electric multiple 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: electric multiple units | Statement: [S25, rollingStockPowerSupply, electric multiple units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rollingStockPowerSupply Context triple: [S25, rollingStockPowerSupply, electric multiple units]
-
A.
rollingStockSupplier
Indicates that one entity supplies or provides rolling stock (such as railway vehicles) to another entity.
-
B.
rollingStockOperator
Indicates that an entity operates or manages rolling stock, such as trains or rail vehicles, in a railway system.
-
C.
rollingStockType
Indicates the specific category or type of railway rolling stock associated with an entity (e.g., locomotive, passenger car, freight wagon).
-
D.
numberOfPowerCars
Indicates the relationship specifying how many power cars (self-propelled units) are associated with or contained in a given train or rail consist.
-
E.
ownedRollingStock
Indicates that one entity possesses or has ownership rights over specific rolling stock (such as trains, railcars, or locomotives).
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0654a88a881908d5cb2aa7f22c4c7 |
completed | March 22, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c064c080148190a7c3218867f1f572 |
completed | March 22, 2026, 9:53 p.m. |
Created at: March 22, 2026, 4:30 p.m.