Triple

T6537292
Position Surface form Disambiguated ID Type / Status
Subject FDR Drive E168195 entity
Predicate hasTrafficRole P20752 FINISHED
Object bypass for local Manhattan streets 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: bypass for local Manhattan streets | Statement: [FDR Drive, hasTrafficRole, bypass for local Manhattan streets]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTrafficRole
Context triple: [FDR Drive, hasTrafficRole, bypass for local Manhattan streets]
  • A. hasTrafficRegime
    Indicates that a specified traffic control or regulatory system applies to a given road, area, or transport context.
  • B. hasTrafficControl
    Indicates that some form of traffic management or regulation mechanism is present or applied to a given route, intersection, or transportation element.
  • C. hasTrafficFunction chosen
    Indicates that an entity performs, supports, or is assigned a specific function or role related to traffic management or control.
  • D. hasTruckTraffic
    Indicates that there is truck-related vehicular movement or flow occurring on or through a specified location or route.
  • E. hasTrafficDirection
    Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
  • 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_69c68a51564081909e93aee0dbd9cca3 completed March 27, 2026, 1:46 p.m.
NER Named-entity recognition batch_69c6ce07332481909a5a7964282eb776 completed March 27, 2026, 6:35 p.m.
PD Predicate disambiguation batch_69c6acf3e3708190b052ec774e607cb7 completed March 27, 2026, 4:14 p.m.
Created at: March 27, 2026, 1:49 p.m.