Triple

T16808357
Position Surface form Disambiguated ID Type / Status
Subject A5 E408536 entity
Predicate connects P390 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: [A5, connects, Biel/Bienne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Biel/Bienne
Context triple: [A5, connects, 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. Stettlen
    Stettlen is a municipality in the canton of Bern in Switzerland, situated just east of the city of Bern and functioning largely as a residential and commuter community.
  • C. Berne
    Berne is the de facto capital city of Switzerland and the seat of its federal government institutions.
  • D. Bülach
    Bülach is a town in northern Switzerland that serves as a regional center near Zurich, known for its residential character and proximity to Zurich Airport.
  • E. Türnich
    Türnich is a district of the town of Kerpen in North Rhine-Westphalia, Germany, known as a residential area within the Cologne metropolitan region.
  • 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_69d88393905081908d00a86b99996ac8 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b2cde590819080dc474292b023ee completed April 18, 2026, 4:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a01481dfcdc8190818456f89c285df4 completed May 11, 2026, 3:08 a.m.
Created at: April 10, 2026, 5:22 a.m.