Triple
T5127475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. intercity passenger rail network |
E115617
|
entity |
| Predicate | includesHighSpeedSegment |
P48478
|
FINISHED |
| Object | Northeast Corridor between Boston and Washington, D.C. |
E2775
|
NE FINISHED |
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: Northeast Corridor between Boston and Washington, D.C. | Statement: [U.S. intercity passenger rail network, includesHighSpeedSegment, Northeast Corridor between Boston and Washington, D.C.]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Northeast Corridor between Boston and Washington, D.C. Context triple: [U.S. intercity passenger rail network, includesHighSpeedSegment, Northeast Corridor between Boston and Washington, D.C.]
-
A.
Northeast Corridor
chosen
The Northeast Corridor is the busiest passenger rail line in the United States, running primarily Amtrak and commuter trains along the urbanized spine of the East Coast between major cities such as Washington, D.C., Philadelphia, New York City, and Boston.
-
B.
Amtrak Northeast Corridor routes
Amtrak Northeast Corridor routes are the heavily traveled passenger rail lines connecting major cities from Boston through New York and Philadelphia to Washington, D.C., forming the busiest and most important rail corridor in the United States.
-
C.
Baltimore–Harrisburg corridor
The Baltimore–Harrisburg corridor is a key Mid-Atlantic transportation and economic region linking Baltimore, Maryland with Harrisburg, Pennsylvania.
-
D.
Amtrak Empire Corridor
The Amtrak Empire Corridor is a major passenger rail route in New York State that connects New York City with Albany and other upstate cities along the Hudson River and beyond.
-
E.
Boston–Portland main line
The Boston–Portland main line is a historic New England railroad corridor connecting Boston, Massachusetts, with Portland, Maine, that has long served as a key passenger and freight route along the region’s coast.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesHighSpeedSegment Context triple: [U.S. intercity passenger rail network, includesHighSpeedSegment, Northeast Corridor between Boston and Washington, D.C.]
-
A.
hasHighSpeedLine
chosen
Indicates that there exists a high-speed rail line connection between the related entities.
-
B.
containsFast
Indicates that one entity includes or holds another entity in a way that allows rapid or high-speed access, interaction, or processing.
-
C.
hasUnrestrictedSpeedSection
Indicates that a route or roadway segment includes a section where no specific maximum speed limit is imposed.
-
D.
hasExpressSegments
Indicates that a route, service, or path includes segments that are designated as express, skipping certain intermediate stops or steps.
-
E.
hasExpresswaySection
Indicates that an entity includes, contains, or is associated with a specific section or segment of an expressway.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bec4beb7b48190a2f4e41a13fdd5f3 |
completed | March 21, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd77aa68b88190a50dd736a72d2901 |
completed | March 20, 2026, 4:36 p.m. |
Created at: March 20, 2026, 1:42 p.m.