Triple

T401307
Position Surface form Disambiguated ID Type / Status
Subject Vernier E9287 entity
Predicate hasNeighboringMunicipality P224 FINISHED
Object Bernex E53379 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: Bernex | Statement: [Vernier, hasNeighboringMunicipality, Bernex]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bernex
Context triple: [Vernier, hasNeighboringMunicipality, Bernex]
  • A. Bernex chosen
    Bernex is a municipality in western Switzerland located near the city of Geneva, known for its semi-rural character and surrounding vineyards.
  • B. Cologny
    Cologny is an affluent municipality on the shores of Lake Geneva in Switzerland, known for its scenic views and as the home of the World Economic Forum’s headquarters.
  • C. Hermance
    Hermance is a small lakeside municipality on the shores of Lake Geneva in southwestern Switzerland.
  • D. Bütgenbach
    Bütgenbach is a municipality in eastern Belgium’s German-speaking Community, known for its scenic lake, outdoor recreation, and proximity to the strategic Elsenborn Ridge.
  • E. Solothurn
    Solothurn is a canton in northwestern Switzerland known for its historic baroque town of the same name and its location along the Aare River.
  • 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_69a2e8004cb88190b92ed1add6abf41a completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2ee2c2d1881909aa1ccfaa4172b38 completed Feb. 28, 2026, 1:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69a5103417008190ab3755dbba5f7622 completed March 2, 2026, 4:21 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.