Triple
T28772351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z 5600 |
E726444
|
entity |
| Predicate | rollingStockCategory |
P1305
|
FINISHED |
| Object | suburban EMU |
—
|
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: suburban EMU | Statement: [Z 5600, rollingStockCategory, suburban EMU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rollingStockCategory Context triple: [Z 5600, rollingStockCategory, suburban EMU]
-
A.
rollingStockType
chosen
Indicates the specific category or type of railway rolling stock associated with an entity (e.g., locomotive, passenger car, freight wagon).
-
B.
rollingStockFamily
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.
ownedRollingStock
Indicates that one entity possesses or has ownership rights over specific rolling stock (such as trains, railcars, or locomotives).
-
D.
rollingStockOperator
Indicates that an entity operates or manages rolling stock, such as trains or rail vehicles, in a railway system.
-
E.
branchLineRollingStock
Indicates that the rolling stock is assigned to or operates on a branch line rather than a main line.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:16 a.m.