Triple

T14155952
Position Surface form Disambiguated ID Type / Status
Subject Frauenkirch E350813 entity
Predicate locatedNear P294 FINISHED
Object Davos Platz E101887 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: Davos Platz | Statement: [Frauenkirch, locatedNear, Davos Platz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Davos Platz
Context triple: [Frauenkirch, locatedNear, Davos Platz]
  • A. Davos Platz chosen
    Davos Platz is the central district of the Swiss Alpine town of Davos, known for hosting major international events and serving as a key hub for tourism and winter sports.
  • B. Schweizer Platz
    Schweizer Platz is a public square in Frankfurt am Main, Germany, known as a local hub in the Sachsenhausen district with shops, cafés, and access to the city’s U-Bahn network.
  • C. Innsbrucker Platz
    Innsbrucker Platz is a public square in Berlin, Germany, known as a local traffic and transport hub in the Schöneberg district.
  • D. Opernplatz
    Opernplatz is a prominent public square in central Frankfurt am Main, Germany, known especially for hosting the historic Alte Oper concert hall.
  • E. Schlossplatz
    Schlossplatz is a historic central square in Berlin that once fronted the Berlin City Palace and now serves as the site of the reconstructed Humboldt Forum.
  • 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_69d8278775fc8190b0802d22ca2f495d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6135744c81909a43d659f5fe2895 completed April 14, 2026, 3:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcf7ec6448819087e50aac964ec637 completed May 7, 2026, 8:37 p.m.
Created at: April 10, 2026, 12:58 a.m.