Triple

T2851783
Position Surface form Disambiguated ID Type / Status
Subject SeaTac E63107 entity
Predicate servedBy P82 FINISHED
Object Link light rail E53254 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: Link light rail | Statement: [SeaTac, servedBy, Link light rail]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Link light rail
Context triple: [SeaTac, servedBy, Link light rail]
  • A. Link light rail chosen
    Link light rail is a regional light rail transit system serving the Seattle metropolitan area in Washington State, operated by Sound Transit.
  • B. Light RailLink
    Light RailLink is a light rail transit system in the Baltimore metropolitan area that provides north–south rail service through the city and its suburbs.
  • C. METRO light rail
    METRO light rail is a rapid transit system serving the Minneapolis–Saint Paul metropolitan area with multiple color-designated lines connecting key urban, suburban, and airport destinations.
  • D. MAX Light Rail
    MAX Light Rail is the metropolitan light rail transit system serving the Portland, Oregon, metropolitan area.
  • E. SPRINTER light rail
    SPRINTER light rail is a diesel multiple-unit light rail service in northern San Diego County, California, connecting Oceanside with inland cities such as Vista, San Marcos, and Escondido.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ab4c407c408190857d25e027155ce9 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdf5ca2648190bd32c6ec4b0dd3b6 completed March 7, 2026, 8:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69b01d81e76c8190aae5e6dd9b13e28b completed March 10, 2026, 1:32 p.m.
Created at: March 6, 2026, 10:02 p.m.