Triple

T18213708
Position Surface form Disambiguated ID Type / Status
Subject Fraubrunnen E436096 entity
Predicate neighboringMunicipality P17964 FINISHED
Object Brunnenthal 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: Brunnenthal | Statement: [Fraubrunnen, neighboringMunicipality, Brunnenthal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brunnenthal
Context triple: [Fraubrunnen, neighboringMunicipality, Brunnenthal]
  • A. Hünenberg
    Hünenberg is a municipality in the canton of Zug in central Switzerland, known for its residential character and location near Lake Zug.
  • B. Bürchen
    Bürchen is a small alpine municipality and popular holiday resort in the canton of Valais in southwestern Switzerland.
  • C. Bettlach chosen
    Bettlach is a Swiss municipality located in the canton of Solothurn.
  • D. Alpthal
    Alpthal is a Swiss alpine village and municipality in the canton of Schwyz, known for its scenic mountain landscape and outdoor recreation opportunities.
  • E. Herisau
    Herisau is a Swiss town that serves as the administrative and economic center of the canton of Appenzell Ausserrhoden.
  • 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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e475953c81909f792793ded2057e completed April 19, 2026, 2:19 p.m.
Created at: April 10, 2026, 10:32 a.m.