Triple
T27199651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rector Street (BMT Broadway Line) |
E683698
|
entity |
| Predicate | hasTracksDirection |
P4069
|
FINISHED |
| Object | northbound |
—
|
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: northbound | Statement: [Rector Street (BMT Broadway Line), hasTracksDirection, northbound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTracksDirection Context triple: [Rector Street (BMT Broadway Line), hasTracksDirection, northbound]
-
A.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
B.
hasTrafficDirection
chosen
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
C.
hasTailTracks
Indicates that an entity exhibits or leaves behind tail-shaped tracks or imprints as evidence of its movement or presence.
-
D.
hasNumberOfDirections
Indicates that an entity is associated with a specific count of possible directions or orientations.
-
E.
hasTrackLanes
Indicates that an entity (such as a road or track) includes one or more designated lanes for vehicle or train movement.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 27, 2026, 9:35 a.m.