Triple
T34079291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norfolk Southern Pittsburgh Line |
E873988
|
entity |
| Predicate | hasNotableCityAlongRoute |
P65699
|
FINISHED |
| Object | Pittsburgh |
E19280
|
NE 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: Pittsburgh | Statement: [Norfolk Southern Pittsburgh Line, hasNotableCityAlongRoute, Pittsburgh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCityAlongRoute Context triple: [Norfolk Southern Pittsburgh Line, hasNotableCityAlongRoute, Pittsburgh]
-
A.
hasMajorCityOnRoute
chosen
Indicates that a major city lies along, or is directly served by, a specified route or path between locations.
-
B.
hasCommercialCorridorAlong
Indicates that a place contains a continuous stretch of commercial activity or businesses situated along a specified linear feature, such as a street or route.
-
C.
isMajorRouteBetweenCapitals
Indicates that a route serves as a primary or significant transportation connection between two capital cities.
-
D.
passesThroughCapital
Indicates that a route, path, or trajectory goes through or intersects the capital city of a given region or country.
-
E.
isKeyNationalRouteFor
Indicates that one route serves as a primary or strategically important national connection for another route or network.
- F. None of above.
Provenance (4 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a02f441bd408190923b6b68adee8fde |
completed | May 12, 2026, 9:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36b75f6794819095da72b7714cff1c |
completed | June 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_6a02f3c1e64881908569423c9f298f26 |
completed | May 12, 2026, 9:32 a.m. |
Created at: May 1, 2026, 1:52 a.m.