Triple

T1470367
Position Surface form Disambiguated ID Type / Status
Subject IND Queens Boulevard Line E27120 entity
Predicate hasExpressService P16277 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: [IND Queens Boulevard Line, hasExpressService, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasExpressService
Context triple: [IND Queens Boulevard Line, hasExpressService, yes]
  • A. hasExpressTracks
    Indicates that a transportation route or facility includes tracks designated for express service, allowing faster travel with fewer stops than regular tracks.
  • B. canExpress
    Indicates that an entity has the ability or capacity to convey, articulate, or communicate something (such as an idea, emotion, or property).
  • C. hasExpressSegments chosen
    Indicates that a route, service, or path includes segments that are designated as express, skipping certain intermediate stops or steps.
  • D. hasInternationalService
    Indicates that an entity provides or is connected to transportation or communication services that operate across national borders.
  • E. hasCargoServices
    Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
  • 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_69a496d25d6881909dbd84f86d763992 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c5d9dd4c8190ba840a9255cd1293 completed March 1, 2026, 11:03 p.m.
PD Predicate disambiguation batch_69a4c48350d88190a81bd149103f93e3 completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8:01 p.m.