Triple
T25850186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOPAC |
E651178
|
entity |
| Predicate | railroadPredecessorOf |
P157699
|
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, railroadPredecessorOf, Union Pacific Railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadPredecessorOf Context triple: [MOPAC, railroadPredecessorOf, Union Pacific Railroad]
-
A.
railroadSuccessor
chosen
Indicates that one railroad entity directly follows or replaces another in an operational or historical succession.
-
B.
railroadLinePredecessor
Indicates that one railroad line is the direct predecessor or earlier version in the historical or organizational sequence of another railroad line.
-
C.
formerRailroad
Indicates that an entity was previously a railroad but no longer functions as one.
-
D.
followsFormerRailroad
Indicates that something is aligned with or traces the route of a former railroad line.
-
E.
railroadOrigin
Indicates that a railroad or rail line begins, originates, or has its starting point at a specified location or entity.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 7:58 a.m.