Triple

T5219082
Position Surface form Disambiguated ID Type / Status
Subject Berner E117823 entity
Predicate usedInDialect P23892 FINISHED
Object Bernese German E17970 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: Bernese German | Statement: [Berner, usedInDialect, Bernese German]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bernese German
Context triple: [Berner, usedInDialect, Bernese German]
  • A. Swiss Germans
    Swiss Germans are a German-speaking ethnic subgroup primarily inhabiting the German-speaking regions of Switzerland, distinguished by their Alemannic dialects and Swiss cultural identity.
  • B. Swiss French
    Swiss French is the variety of the French language spoken in the French‑speaking regions of Switzerland, characterized by distinctive vocabulary, pronunciation, and some regional usages.
  • C. Alemannic German chosen
    Alemannic German is a group of Upper German dialects spoken primarily in parts of Switzerland, Germany, Austria, and Liechtenstein.
  • D. Berner
    A Berner is a resident or native of the Swiss city of Bern.
  • E. Romandy
    Romandy is the French-speaking western region of Switzerland, encompassing cantons such as Geneva, Vaud, Neuchâtel, and Jura.
  • 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_69bd4465e03081909bfcfd7113062590 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7ab6e63c8190964b2b65a0206134 completed March 20, 2026, 4:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69beeff0b15081908741aadfd351811c completed March 21, 2026, 7:22 p.m.
Created at: March 20, 2026, 1:48 p.m.