Triple

T15019482
Position Surface form Disambiguated ID Type / Status
Subject Jura bernois E378045 entity
Predicate contains P35 FINISHED
Object Tavannes E592863 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: Tavannes | Statement: [Jura bernois, contains, Tavannes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tavannes
Context triple: [Jura bernois, contains, Tavannes]
  • A. Tavannes chosen
    Tavannes is a municipality in the Jura bernois administrative district of the canton of Bern in Switzerland, known for its watchmaking heritage and location in the Jura Mountains.
  • B. Stabio
    Stabio is a municipality in the canton of Ticino in southern Switzerland, near the Italian border.
  • C. Vésenaz
    Vésenaz is a residential village in the canton of Geneva, Switzerland, situated on the shores of Lake Geneva and forming part of the municipality of Collonge-Bellerive.
  • D. Blevio
    Blevio is a small lakeside municipality in the Province of Como, Lombardy, Italy, situated on the eastern shore of Lake Como.
  • E. Plessur
    Plessur is a river in the canton of Graubünden in eastern Switzerland that flows through the city of Chur before joining the Alpine Rhine.
  • 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_69d85cd3a3c881908c71fc424d459c17 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded76445988190984b57de66e00c4a completed April 15, 2026, 12:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe96af719881909906adfd6cb508aa completed May 9, 2026, 2:06 a.m.
Created at: April 10, 2026, 2:56 a.m.