Triple

T3848680
Position Surface form Disambiguated ID Type / Status
Subject Nollendorfplatz area E85235 entity
Predicate servedBy P82 FINISHED
Object U3 line E300311 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: U3 line | Statement: [Nollendorfplatz area, servedBy, U3 line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: U3 line
Context triple: [Nollendorfplatz area, servedBy, U3 line]
  • A. U3 line chosen
    The U3 line is a route of the Frankfurt U-Bahn rapid transit system that connects central Frankfurt with its northwestern suburbs.
  • B. U1 line
    The U1 line is a route of the Frankfurt U-Bahn rapid transit system that connects central Frankfurt with several northern suburbs.
  • C. 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.
  • D. 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.
  • E. U1 metro line
    The U1 metro line is one of Vienna’s main underground lines, running north–south through the city and connecting key districts and transport hubs.
  • 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_69aed936de1c81908f91bed80f70abb2 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeebcc8a0481909c35161336bdfbf9 completed March 9, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5122eb2708190b1aa9da233481015 completed March 14, 2026, 7:45 a.m.
Created at: March 9, 2026, 3:19 p.m.