Triple

T10947736
Position Surface form Disambiguated ID Type / Status
Subject Führerbau E258640 entity
Predicate near P350 FINISHED
Object Königsplatz E801577 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: Königsplatz | Statement: [Führerbau, near, Königsplatz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Königsplatz
Context triple: [Führerbau, near, Königsplatz]
  • A. Königsplatz
    Königsplatz is a central square in the Bavarian city of Fürth, Germany, known as an important local transport and urban hub.
  • B. Königsplatz chosen
    Königsplatz is a historic square in Berlin that played a significant role in the city’s political and cultural life, especially during the 19th and early 20th centuries.
  • C. Savignyplatz
    Savignyplatz is a well-known square and surrounding neighborhood in Berlin’s Charlottenburg district, noted for its lively cafés, restaurants, and historic urban charm.
  • D. Stephansplatz
    Stephansplatz is the central square of Vienna, Austria, known for its historic architecture and as the site of St. Stephen's Cathedral.
  • E. Opernplatz
    Opernplatz is a prominent public square in central Frankfurt am Main, Germany, known especially for hosting the historic Alte Oper concert hall.
  • 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_69d6aa8769b4819082bfe5e61b9017f0 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d770ebac3c8190849ddda3d9d37327 completed April 9, 2026, 9:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69e23c4a75688190894c83b8964509a6 completed April 17, 2026, 1:57 p.m.
Created at: April 8, 2026, 9:23 p.m.