Triple

T35098889
Position Surface form Disambiguated ID Type / Status
Subject NY Ave NE E1012947 entity
Predicate isFreightRoute P42526 FINISHED
Object yes 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: yes | Statement: [NY Ave NE, isFreightRoute, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isFreightRoute
Context triple: [NY Ave NE, isFreightRoute, yes]
  • A. isOnFreightRoute chosen
    Indicates that something lies along or is included within a designated freight transportation route used for moving goods.
  • B. isKeyFreightRoute
    Indicates that a transportation route serves as a primary or strategically important corridor for moving freight.
  • C. isFreightService
    Indicates that the referenced service operates as a freight or cargo transportation service rather than a passenger service.
  • D. isFreightIntensive
    Indicates that an activity, process, or operation involves a high volume or intensity of freight movement or transportation.
  • E. isFreightOnlyCode
    Indicates that something is designated exclusively for freight use and not intended for passenger or mixed-service purposes.
  • 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_69f76dd556248190808b4c4f43debebb completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78ce78b508190955848e133398dc8 completed May 3, 2026, 5:59 p.m.
PD Predicate disambiguation batch_69f78b8f4cc08190b49fccd798cb25d7 completed May 3, 2026, 5:53 p.m.
Created at: May 3, 2026, 4:01 p.m.