Triple

T24725399
Position Surface form Disambiguated ID Type / Status
Subject M23 SBS E618131 entity
Predicate transitCorridor P3034 FINISHED
Object 23rd Street Crosstown 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: 23rd Street Crosstown | Statement: [M23 SBS, transitCorridor, 23rd Street Crosstown]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transitCorridor
Context triple: [M23 SBS, transitCorridor, 23rd Street Crosstown]
  • A. transportCorridor chosen
    Indicates a route or pathway used to move people, goods, or resources between locations.
  • B. parallelTransportCorridor
    Indicates a relationship where one path, route, or connection is used to transport something in a way that preserves its structure or configuration relative to another, typically along a shared or corresponding trajectory.
  • C. transportationCorridorType
    Indicates the specific kind or classification of a transportation corridor (such as road, rail, or waterway) that characterizes how the route is used for movement or transit.
  • D. commuterCorridorFor
    Indicates a route or area that serves as a primary pathway for regular travel between two locations, typically used by commuters.
  • E. rapidTransitSystem
    Indicates a transportation relationship where people or goods are moved via a high-capacity, high-frequency public transit system designed for rapid travel over urban or regional routes.
  • 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_69e2fab772608190b74163751047ff50 completed April 18, 2026, 3:29 a.m.
NER Named-entity recognition batch_69f44a417a58819081777e18dda149fd completed May 1, 2026, 6:37 a.m.
PD Predicate disambiguation batch_69f442a977b08190b44eac040cb90211 completed May 1, 2026, 6:05 a.m.
Created at: April 18, 2026, 3:56 a.m.