Triple
T8240825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canal Street (Manhattan Bridge Line) |
E192528
|
entity |
| Predicate | isOnManhattanBridgeRoute |
P57605
|
FINISHED |
| Object | B train |
—
|
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: B train | Statement: [Canal Street (Manhattan Bridge Line), isOnManhattanBridgeRoute, B train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnManhattanBridgeRoute Context triple: [Canal Street (Manhattan Bridge Line), isOnManhattanBridgeRoute, B train]
-
A.
onSideOfManhattan
Indicates that one entity is located on the same side of Manhattan as, or relative to, another reference entity.
-
B.
manhattanBridgeTrack
chosen
Indicates a connection or route that follows or uses the Manhattan Bridge as its primary path or segment.
-
C.
isNorthernManhattanTerminalFor
Indicates that one location serves as the northern Manhattan terminal endpoint for a specified transit line or route.
-
D.
bronxLine
Indicates a relationship where something is part of, associated with, or runs along the Bronx transit or route line.
-
E.
ManhattanPortalLocatedIn
Indicates that a specific portal or gateway is situated within the geographic area of Manhattan.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb783e13648190abf34eb8c244ea17 |
completed | March 31, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.