Triple

T31953047
Position Surface form Disambiguated ID Type / Status
Subject Boston–Los Angeles E815831 entity
Predicate hasNonstopService P94244 FINISHED
Object true 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: true | Statement: [Boston–Los Angeles, hasNonstopService, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNonstopService
Context triple: [Boston–Los Angeles, hasNonstopService, true]
  • A. isNonStop chosen
    Indicates that a service, trip, or process occurs from start to finish without any intermediate stops or interruptions.
  • B. servedNonstopBy
    Indicates that there is a direct, uninterrupted service (e.g., a route or connection) operating between two entities without any intermediate stops or transfers.
  • C. hasTransitServiceType
    Indicates that a transit service is associated with a specific type or category of service (e.g., bus, rail, express).
  • D. hasRailServiceAt
    Indicates that a rail transport service operates at or serves a particular location or facility.
  • E. hasDirectServices
    Indicates that one entity provides services directly to another entity without intermediaries.
  • 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_69f348f4ec708190abbb2a7c3ed58844 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_6a00d08e8fac8190b59359134e6e1c03 completed May 10, 2026, 6:38 p.m.
PD Predicate disambiguation batch_6a00d0127c088190a6f5b360450af113 completed May 10, 2026, 6:36 p.m.
Created at: May 1, 2026, 12:08 a.m.