Triple

T333976
Position Surface form Disambiguated ID Type / Status
Subject JFK/UMass E6682 entity
Predicate connectsViaShuttle P3493 FINISHED
Object JFK Presidential Library shuttle bus 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: JFK Presidential Library shuttle bus | Statement: [JFK/UMass, connectsViaShuttle, JFK Presidential Library shuttle bus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsViaShuttle
Context triple: [JFK/UMass, connectsViaShuttle, JFK Presidential Library shuttle bus]
  • A. hasShuttleLine chosen
    Indicates that there is a shuttle service or route operating between the related entities.
  • B. hasPassengerTerminal
    Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
  • C. hasPublicTransportConnection
    Indicates that there is an available public transportation link or service connecting the related entities.
  • D. hasTransportHub
    Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
  • E. connectsTo
    Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
  • 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_69a2e79434908190a9d5afe415153ad9 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eac641708190b85fa21368e5de8e completed Feb. 28, 2026, 1:16 p.m.
PD Predicate disambiguation batch_69a2e94d99cc8190a112e4b630ec63c1 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.