Triple

T17308785
Position Surface form Disambiguated ID Type / Status
Subject Friedrichshain-Kreuzberg E420234 entity
Predicate hasPublicTransport P1288 FINISHED
Object U5 line NE ONNED1

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: U5 line | Statement: [Friedrichshain-Kreuzberg, hasPublicTransport, U5 line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: U5 line
Context triple: [Friedrichshain-Kreuzberg, hasPublicTransport, U5 line]
  • A. U5 line chosen
    The U5 line is a major Berlin U-Bahn route running east–west that connects central hubs like Alexanderplatz with eastern districts of the city.
  • B. U6 line
    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.
  • C. U4 line
    The U4 line is one of Berlin's U-Bahn subway lines, running a short route in the inner city and connecting key stations including Nollendorfplatz.
  • 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. U1 line
    The U1 line is one of Berlin’s U-Bahn metro lines, running primarily east–west and serving central districts including Friedrichshain-Kreuzberg.
  • 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_6a01954cfd048190b201c5e457c2a4a2 in_progress May 11, 2026, 8:37 a.m.
Created at: April 10, 2026, 5:43 a.m.