Triple
T16194285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Pacific Challenger |
E393021
|
entity |
| Predicate | farePositioning |
P106903
|
FINISHED |
| Object | below premier streamliner services |
—
|
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: below premier streamliner services | Statement: [Union Pacific Challenger, farePositioning, below premier streamliner services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: farePositioning Context triple: [Union Pacific Challenger, farePositioning, below premier streamliner services]
-
A.
rackPosition
Indicates the spatial placement or slot of an item within a rack or racking system.
-
B.
fareControlUnifiedWith
Indicates that separate fare control areas are combined into a single, shared fare-controlled zone.
-
C.
fareContext
chosen
Indicates the pricing or fare-related conditions under which a transaction, service, or travel arrangement is applied.
-
D.
ridingPosition
Indicates the relative physical placement or posture of an entity while it is riding or being carried by another entity.
-
E.
positioningSystems
Indicates a relationship where systems are used to determine, track, or control the spatial position or location of entities.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222d851188190b2452d165e4fc4bd |
completed | April 17, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.