Triple
T27235276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MoPac |
E682254
|
entity |
| Predicate | followsRailCorridorOf |
P70018
|
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: [MoPac, followsRailCorridorOf, Union Pacific Railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsRailCorridorOf Context triple: [MoPac, followsRailCorridorOf, Union Pacific Railroad]
-
A.
servesRailCorridor
Indicates that something (such as a service, facility, or operation) provides service to or operates along a specific rail corridor.
-
B.
partOfRailwayCorridor
Indicates that one entity is a segment, component, or area belonging to or contained within a specific railway corridor.
-
C.
followsRailroad
chosen
Indicates that one entity is aligned with or travels along the path defined by a railroad.
-
D.
railwayRunsAlong
Indicates that a railway line extends parallel to and in close proximity with another feature or route for a significant distance.
-
E.
railCorridorType
Indicates the specific classification or type of a rail corridor associated with the subject (e.g., mainline, branch line, high-speed, freight, etc.).
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 9:47 a.m.