Triple
T23393734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salisbury Mills–Cornwall station |
E594090
|
entity |
| Predicate | primaryDirectionOfTravel |
P73274
|
FINISHED |
| Object | toward New York City area |
—
|
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: toward New York City area | Statement: [Salisbury Mills–Cornwall station, primaryDirectionOfTravel, toward New York City area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDirectionOfTravel Context triple: [Salisbury Mills–Cornwall station, primaryDirectionOfTravel, toward New York City area]
-
A.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
B.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
C.
travelsDirection
chosen
Indicates that an entity moves or is transported in a specified directional heading or orientation.
-
D.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
-
E.
mainStraightDirection
Indicates the direction in which the primary or central straight path or segment is oriented or extends.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a49eb3b881909da7f1c47c67c81f |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:36 p.m.