Triple

T17726001
Position Surface form Disambiguated ID Type / Status
Subject Frankfurt Alte Oper U-Bahn station E442461 entity
Predicate servedByLine P1293 FINISHED
Object U7 NE NERFINISHED

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: U7 | Statement: [Frankfurt Alte Oper U-Bahn station, servedByLine, U7]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: U7
Context triple: [Frankfurt Alte Oper U-Bahn station, servedByLine, U7]
  • A. U7
    U7 is a line of the Berlin U-Bahn rapid transit system, running in an east–west direction across the city.
  • B. U7 chosen
    U7 is a line of the Frankfurt U-Bahn rapid transit network serving various districts across the city.
  • C. U7
    U7 is a supplementary line of the Munich U-Bahn rapid transit system, typically operating as a reinforcement or special service on existing routes.
  • D. U7
    U7 is a light rail line of the Stuttgart Stadtbahn network in Germany, providing urban transit service across parts of the Stuttgart metropolitan area.
  • E. U9
    U9 is a Berlin U-Bahn subway line that serves the Wedding district among other areas in the city.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9ec79688190b86bdcef85a7b3aa completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e478e25a80819096289fba4ecb227f completed April 19, 2026, 6:40 a.m.
Created at: April 10, 2026, 10:07 a.m.