Triple
T31978497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunters Point Avenue (IRT Flushing Line, Manhattan-bound) |
E816511
|
entity |
| Predicate | hasTrackDirection |
P153865
|
FINISHED |
| Object | westbound |
—
|
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: westbound | Statement: [Hunters Point Avenue (IRT Flushing Line, Manhattan-bound), hasTrackDirection, westbound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackDirection Context triple: [Hunters Point Avenue (IRT Flushing Line, Manhattan-bound), hasTrackDirection, westbound]
-
A.
hotspotTrackDirection
chosen
Indicates the direction in which a hotspot or tracked point of interest is moving or being followed over time.
-
B.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
C.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
D.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
E.
hasRouteDirection
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: May 1, 2026, 12:11 a.m.