Triple

T21007611
Position Surface form Disambiguated ID Type / Status
Subject Grödig E517452 entity
Predicate hasNeighbour P5707 FINISHED
Object Wals-Siezenheim 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: Wals-Siezenheim | Statement: [Grödig, hasNeighbour, Wals-Siezenheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wals-Siezenheim
Context triple: [Grödig, hasNeighbour, Wals-Siezenheim]
  • A. Wals-Siezenheim chosen
    Wals-Siezenheim is a municipality in the Austrian state of Salzburg, known for its proximity to the city of Salzburg and for hosting the Red Bull Arena football stadium.
  • B. Zwiesel
    Zwiesel is a prominent mountain in the Bavarian Alps of southeastern Germany, known for its scenic hiking routes and panoramic views over the Bad Reichenhall area.
  • C. Zwiesel
    Zwiesel is a small Bavarian town in southeastern Germany known for its glassmaking tradition and its location on the edge of the Bavarian Forest.
  • D. Schönteichen
    Schönteichen is a small municipality in the Free State of Saxony in eastern Germany.
  • E. Wörth an der Isar
    Wörth an der Isar is a small municipality in Lower Bavaria, Germany, situated on the river Isar and characterized by its rural setting and proximity to the city of Landshut.
  • 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_69e0b50192308190a284fcc89dd23a49 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc3cc8648190b1a419ef734a69e6 completed April 21, 2026, 4:25 a.m.
Created at: April 16, 2026, 1:53 p.m.