Triple
T24118694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M4 railcar |
E597589
|
entity |
| Predicate | railwayTrafficMode |
P18634
|
FINISHED |
| Object | heavy rail |
—
|
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: heavy rail | Statement: [M4 railcar, railwayTrafficMode, heavy rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayTrafficMode Context triple: [M4 railcar, railwayTrafficMode, heavy rail]
-
A.
railwayTraffic
Indicates the presence, flow, or management of train movements along railway lines between locations.
-
B.
railwayTrafficDirection
Indicates the customary side of the track on which trains are operated or expected to run within a given railway system or segment.
-
C.
railSystemType
chosen
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
D.
coordinatesRailTrafficWith
Indicates that one entity organizes and synchronizes rail operations or movements with another entity to ensure coordinated train traffic.
-
E.
railwayTrafficRole
Indicates the specific function or responsibility an entity has within the operation, management, or control of railway traffic.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee1a2608190870ade02495c5ebe |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:05 p.m.