Triple

T34283140
Position Surface form Disambiguated ID Type / Status
Subject Broadway and 191st Street E879651 entity
Predicate subwayAccessRole P81720 FINISHED
Object access point to nearby subway services 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: access point to nearby subway services | Statement: [Broadway and 191st Street, subwayAccessRole, access point to nearby subway services]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subwayAccessRole
Context triple: [Broadway and 191st Street, subwayAccessRole, access point to nearby subway services]
  • A. undergroundRailroadRole
    Indicates the specific role or function an entity played within the operations or support network of the Underground Railroad.
  • B. hasSubwayStationEntrance chosen
    Indicates that one entity serves as an entrance or access point to a subway station associated with another entity.
  • C. hasSubway
    Indicates that a place is served by or contains a subway (metro) system.
  • D. hasPublicTransitRole
    Indicates that an entity holds a specific functional role or responsibility within a public transit system.
  • E. subwayOperation
    Indicates the operation or running of a subway system, relating transit services to the times, routes, or conditions under which subway trains are in service.
  • 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_69f349b5f6648190b9420d94a4cd16e0 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71362f1448190985a80ce7af475cb completed May 3, 2026, 9:20 a.m.
PD Predicate disambiguation batch_69f7127884388190884f23d181a65d19 completed May 3, 2026, 9:16 a.m.
Created at: May 1, 2026, 1:57 a.m.