Triple
T22065838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania Railroad tracks |
E545265
|
entity |
| Predicate | includesMajorRoute |
P89731
|
FINISHED |
| Object | New York–Philadelphia corridor |
—
|
NE NERFINISHED |
How this triple was built (3 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: New York–Philadelphia corridor | Statement: [Pennsylvania Railroad tracks, includesMajorRoute, New York–Philadelphia corridor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: New York–Philadelphia corridor Context triple: [Pennsylvania Railroad tracks, includesMajorRoute, New York–Philadelphia corridor]
-
A.
New York–Scranton corridor
The New York–Scranton corridor is a historically significant rail route linking New York City with Scranton, Pennsylvania, that served as a key passenger and freight artery in the northeastern United States.
-
B.
Philadelphia–Camden corridor
The Philadelphia–Camden corridor is a major bi-state urban and transportation axis linking Philadelphia, Pennsylvania, with Camden, New Jersey, and surrounding communities.
-
C.
Buffalo–Scranton corridor
The Buffalo–Scranton corridor is a historically significant organized-crime territory in the northeastern United States, spanning parts of upstate New York and northeastern Pennsylvania.
-
D.
Baltimore–Harrisburg corridor
The Baltimore–Harrisburg corridor is a key Mid-Atlantic transportation and economic region linking Baltimore, Maryland with Harrisburg, Pennsylvania.
-
E.
New Hampshire–New York City corridor
The New Hampshire–New York City corridor is a major intercity travel route linking communities in New Hampshire with New York City, heavily used for regional commuter and long-distance bus service.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: New York–Philadelphia corridor Target entity description: The New York–Philadelphia corridor is a heavily traveled stretch of the Northeast megalopolis linking New York City and Philadelphia, known for its dense population, intense commuter and intercity traffic, and extensive rail and highway infrastructure.
-
A.
New York–Scranton corridor
The New York–Scranton corridor is a historically significant rail route linking New York City with Scranton, Pennsylvania, that served as a key passenger and freight artery in the northeastern United States.
-
B.
Philadelphia–Camden corridor
The Philadelphia–Camden corridor is a major bi-state urban and transportation axis linking Philadelphia, Pennsylvania, with Camden, New Jersey, and surrounding communities.
-
C.
Buffalo–Scranton corridor
The Buffalo–Scranton corridor is a historically significant organized-crime territory in the northeastern United States, spanning parts of upstate New York and northeastern Pennsylvania.
-
D.
Baltimore–Harrisburg corridor
The Baltimore–Harrisburg corridor is a key Mid-Atlantic transportation and economic region linking Baltimore, Maryland with Harrisburg, Pennsylvania.
-
E.
New Hampshire–New York City corridor
The New Hampshire–New York City corridor is a major intercity travel route linking communities in New Hampshire with New York City, heavily used for regional commuter and long-distance bus service.
- F. None of above. chosen
Provenance (2 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12883d2108190a6127783f8f635fc |
completed | April 28, 2026, 9:37 p.m. |
Created at: April 16, 2026, 8:27 p.m.