Triple

T35044069
Position Surface form Disambiguated ID Type / Status
Subject LIRR Main Line trains E1011147 entity
Predicate primaryCorridorBetween P152997 FINISHED
Object New York City E40 NE 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: New York City | Statement: [LIRR Main Line trains, primaryCorridorBetween, New York City]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryCorridorBetween
Context triple: [LIRR Main Line trains, primaryCorridorBetween, New York City]
  • A. primaryCorridorServed
    Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
  • 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. isMainCorridor
    Indicates that a corridor serves as the primary or central passageway within a building or structure.
  • D. transportCorridor
    Indicates a route or pathway used to move people, goods, or resources between locations.
  • E. primaryRouteThrough chosen
    Indicates that one location or path serves as the main or most significant route passing through another location or area.
  • F. None of above.

Provenance (4 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_69f76dcfdda48190b1ebae5da8b54f12 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a037c8c34f88190ace26f555827f23e completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3803f082c48190b07a687d1b5a0b19 completed June 21, 2026, 3:32 p.m.
PD Predicate disambiguation batch_6a037a016960819093ed4990fb4d9d36 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:01 p.m.