Triple

T17233037
Position Surface form Disambiguated ID Type / Status
Subject South End, Charlotte E418291 entity
Predicate traversedBy P225 FINISHED
Object Lynx Blue Line E176113 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: Lynx Blue Line | Statement: [South End, Charlotte, traversedBy, Lynx Blue Line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lynx Blue Line
Context triple: [South End, Charlotte, traversedBy, Lynx Blue Line]
  • A. Lynx Blue Line chosen
    The Lynx Blue Line is a major light rail transit route serving Charlotte, North Carolina, connecting Uptown with surrounding neighborhoods and suburbs.
  • B. A Line (formerly Blue Line)
    A Line (formerly Blue Line) is a light rail line in Los Angeles County that runs between downtown Los Angeles and Long Beach as part of the Los Angeles Metro Rail system.
  • C. Blue Line
    The Blue Line is one of the main lines of the Lisbon Metro system, serving key central and northern areas of Portugal’s capital city.
  • D. Blue Line
    The Blue Line is one of the Montreal Metro’s rapid transit lines, running east–west to serve several central and northeastern neighborhoods of the city.
  • E. Blue Line
    The Blue Line is one of the primary routes of the MetroLink light rail system serving the St. Louis metropolitan area.
  • 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_69d886d8e96081909870bff6c3d0bf09 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42df9558481909e2e50ae0b02acf7 completed April 19, 2026, 1:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a018c3abb1c819083e802ac79ff4c34 completed May 11, 2026, 7:58 a.m.
Created at: April 10, 2026, 5:39 a.m.