Triple

T19734160
Position Surface form Disambiguated ID Type / Status
Subject Schauplatzgasse E473931 entity
Predicate locatedNear P294 FINISHED
Object Bundesplatz NE NERFINISHED

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: Bundesplatz | Statement: [Schauplatzgasse, locatedNear, Bundesplatz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bundesplatz
Context triple: [Schauplatzgasse, locatedNear, Bundesplatz]
  • A. Bundesplatz
    Bundesplatz is a public square and transport hub in Berlin that serves as an important interchange point for city and suburban rail services.
  • B. Bundesplatz chosen
    Bundesplatz is the central public square in Bern, Switzerland, located in front of the Federal Palace and often used for political events, markets, and public gatherings.
  • C. Konkordiaplatz
    Konkordiaplatz is a vast glacial basin in the Bernese Alps where several major glaciers, including the Aletsch Glacier, converge.
  • D. Europaplatz
    Europaplatz is a public square in Munich, Germany, known as a local transport and urban hub within the city.
  • 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 (2 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_69d8e517ebd48190979ee76723bcfadf completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6515b4d308190af3be1787fa7c65b completed April 20, 2026, 4:16 p.m.
Created at: April 10, 2026, 1:47 p.m.