Triple

T17308788
Position Surface form Disambiguated ID Type / Status
Subject Friedrichshain-Kreuzberg E420234 entity
Predicate hasPublicTransport P1288 FINISHED
Object U8 line E530781 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: U8 line | Statement: [Friedrichshain-Kreuzberg, hasPublicTransport, U8 line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: U8 line
Context triple: [Friedrichshain-Kreuzberg, hasPublicTransport, U8 line]
  • A. U8
    U8 is a line of the Frankfurt U-Bahn rapid transit network serving parts of Frankfurt and its surrounding areas.
  • B. U8
    U8 is a former temporary line designation of the Munich U-Bahn rapid transit system, used primarily for special or reinforcement services rather than as a regular, permanent route.
  • C. U8 chosen
    U8 is a major north–south line of the Berlin U-Bahn rapid transit system, connecting districts such as Gesundbrunnen, Mitte, and Neukölln.
  • D. U8
    U8 is a light rail line of the Stuttgart Stadtbahn network serving various districts in and around Stuttgart, Germany.
  • E. U9 line
    The U9 line is a major Berlin U-Bahn subway route running north–south through the city and serving districts such as Wilmersdorf.
  • 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_69d889d22b848190a4663d0b8f8f76e7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43900eca88190930af0e4ec4fc0f9 completed April 19, 2026, 2:08 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0180e30934819087b7c838c8874aff completed May 11, 2026, 7:10 a.m.
Created at: April 10, 2026, 5:43 a.m.