Triple
T26524073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago–St. Louis rail corridor |
E670636
|
entity |
| Predicate | operatorFreightServices |
P39220
|
FINISHED |
| Object | Union Pacific Railroad |
—
|
NE NERFINISHED |
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: Union Pacific Railroad | Statement: [Chicago–St. Louis rail corridor, operatorFreightServices, Union Pacific Railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorFreightServices Context triple: [Chicago–St. Louis rail corridor, operatorFreightServices, Union Pacific Railroad]
-
A.
operatedFreightServiceIn
Indicates that an entity operated a freight transportation service within or across the specified geographic area or route.
-
B.
freightConnections
Indicates the existence or characteristics of transportation links used to move freight or cargo between locations or entities.
-
C.
freightOperatorOnCorridor
chosen
Indicates that a particular freight operator provides services or operates along a specified transport corridor.
-
D.
freightType
Indicates the category or mode of freight associated with a shipment or transport activity.
-
E.
operatedFreightInterchangeWith
Indicates that one entity operated a freight interchange service or facility jointly with another entity, enabling the transfer of freight between their respective operations.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 27, 2026, 1:30 a.m.