Triple
T22118730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canarsie Line |
E546606
|
entity |
| Predicate | followsStreetCorridor |
P113763
|
FINISHED |
| Object | 14th Street in Manhattan |
—
|
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: 14th Street in Manhattan | Statement: [Canarsie Line, followsStreetCorridor, 14th Street in Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsStreetCorridor Context triple: [Canarsie Line, followsStreetCorridor, 14th Street in Manhattan]
-
A.
followedCorridor
chosen
Indicates that an entity moved along and stayed within the path of a corridor from one point to another.
-
B.
roadCorridorIncludes
Indicates that a specified road corridor spatially contains or encompasses another element or segment within its defined bounds.
-
C.
streetOrientedAlong
Indicates that a street is aligned or runs in the same general direction as a specified reference feature or axis.
-
D.
lineCorridor
Indicates that one entity is a corridor represented or approximated by a line, typically modeling a narrow passageway or path between areas.
-
E.
hasStreetDirection
Indicates that a street or road segment is associated with a specific directional orientation (e.g., northbound, east-west).
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1294fcf2c81909b610e03a0f1921f |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.