Triple

T162883
Position Surface form Disambiguated ID Type / Status
Subject Romandy E2947 entity
Predicate majorCity P316 FINISHED
Object Biel/Bienne E24186 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: Biel/Bienne | Statement: [Romandy, majorCity, Biel/Bienne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Biel/Bienne
Context triple: [Romandy, majorCity, Biel/Bienne]
  • A. Biel/Bienne chosen
    Biel/Bienne is a bilingual (German-French) Swiss city in the canton of Bern, known for its watchmaking industry and location at the eastern end of Lake Biel.
  • B. 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.
  • C. Neuchâtel
    Neuchâtel is a French-speaking canton in western Switzerland known for its lakeside capital, watchmaking industry, and historic architecture.
  • D. Fribourg
    Fribourg is a bilingual Swiss canton in western Switzerland known for its medieval capital city and location at the cultural boundary between French- and German-speaking regions.
  • E. Basel-Stadt
    Basel-Stadt is a small, urban Swiss canton centered on the city of Basel, a major cultural and economic hub in northwestern Switzerland.
  • 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_69a2524ce1e48190ab066bf72859f474 completed Feb. 28, 2026, 2:26 a.m.
NER Named-entity recognition batch_69a2585a1a6481908899ad51211950e8 completed Feb. 28, 2026, 2:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69a3faf665a08190a9ce9fecfd057eae completed March 1, 2026, 8:38 a.m.
Created at: Feb. 28, 2026, 2:34 a.m.