Triple

T3435981
Position Surface form Disambiguated ID Type / Status
Subject Seestraße E72451 entity
Predicate isOnLine P15096 FINISHED
Object U6 line E308543 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: U6 line | Statement: [Seestraße, isOnLine, U6 line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: U6 line
Context triple: [Seestraße, isOnLine, U6 line]
  • A. U6 line chosen
    The U6 line is a route of the Frankfurt U-Bahn rapid transit system that connects various districts across the city, including central hubs such as Hauptwache.
  • B. U7 line
    The U7 line is a route of the Frankfurt U-Bahn rapid transit system that runs across the city and serves major central stations including Hauptwache.
  • C. S6 line
    The S6 line is a route of the Rhine-Main S-Bahn network serving the Frankfurt metropolitan area and connecting central Frankfurt with surrounding suburbs and towns.
  • D. U1 line
    The U1 line is a route of the Frankfurt U-Bahn rapid transit system that connects central Frankfurt with several northern suburbs.
  • E. U3 line
    The U3 line is a route of the Frankfurt U-Bahn rapid transit system that connects central Frankfurt with its northwestern suburbs.
  • 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_69ad85af50288190a854b76653deee6f completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb9f2e4b4819085336fb539daf3c7 completed March 8, 2026, 6:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69b35481a03c81908fd69da55d81aca3 completed March 13, 2026, 12:04 a.m.
Created at: March 8, 2026, 3:16 p.m.