Triple
T19810880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White River Junction station |
E475939
|
entity |
| Predicate | hasFreightConnections |
P101320
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [White River Junction station, hasFreightConnections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFreightConnections Context triple: [White River Junction station, hasFreightConnections, yes]
-
A.
freightConnections
chosen
Indicates the existence or characteristics of transportation links used to move freight or cargo between locations or entities.
-
B.
isOnFreightRoute
Indicates that something lies along or is included within a designated freight transportation route used for moving goods.
-
C.
hasFreightFacility
Indicates that an entity is equipped with or connected to a facility used for handling, loading, unloading, or storing freight.
-
D.
servesAsCargoHubFor
Indicates that one entity functions as a central location or facility for handling, consolidating, and distributing cargo associated with another entity.
-
E.
hasBridgeOrFerryConnection
Indicates that there exists a bridge or ferry link enabling direct passage or transport between the related entities.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6542bd7a48190acf67db41f1131c9 |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.