Triple

T4728565
Position Surface form Disambiguated ID Type / Status
Subject Skokie Swift E104945 entity
Predicate hasRouteNumber P1864 FINISHED
Object Yellow Line E19116 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: Yellow Line | Statement: [Skokie Swift, hasRouteNumber, Yellow Line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yellow Line
Context triple: [Skokie Swift, hasRouteNumber, Yellow Line]
  • A. Yellow Line
    The Yellow Line is one of the color-coded rapid transit routes in the Washington Metro system, running primarily in a north–south direction and serving key areas in Washington, D.C. and Northern Virginia.
  • B. Yellow Line
    The Yellow Line is one of the primary passenger rail routes of the Tyne and Wear Metro rapid transit system serving the Newcastle upon Tyne area in North East England.
  • C. Yellow Line
    The Yellow Line is a designated route within the Baltimore Light Rail system that serves as one of its primary color-coded service lines.
  • D. Yellow Line
    The Yellow Line is Budapest’s historic Metro Line 1, one of the world’s oldest underground railway lines and a key route running beneath Andrássy Avenue.
  • E. Yellow Line chosen
    The Yellow Line is a rapid transit route in Chicago's 'L' system that connects the northern suburb of Skokie to the city's rail network.
  • 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_69bd43ed84648190ae0b7ee8e8d00482 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd644a0ef88190a46230446dfff635 completed March 20, 2026, 3:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69bee059e7088190a04124e5918a3c42 completed March 21, 2026, 6:15 p.m.
Created at: March 20, 2026, 1:18 p.m.