Triple

T907173
Position Surface form Disambiguated ID Type / Status
Subject Alsace E19573 entity
Predicate hasRegionalLanguage P2982 FINISHED
Object Alsatian 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: Alsatian | Statement: [Alsace, hasRegionalLanguage, Alsatian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alsatian
Context triple: [Alsace, hasRegionalLanguage, Alsatian]
  • A. Romandy
    Romandy is the French-speaking western region of Switzerland, encompassing cantons such as Geneva, Vaud, Neuchâtel, and Jura.
  • B. Franco-Provençal (Arpitan)
    Franco-Provençal (Arpitan) is a Romance language historically spoken in parts of France, Switzerland, and Italy, distinct from both French and Occitan and now considered endangered.
  • C. Alemannic German chosen
    Alemannic German is a group of Upper German dialects spoken primarily in parts of Switzerland, Germany, Austria, and Liechtenstein.
  • D. German-speaking Lorraine
    German-speaking Lorraine is a historically Germanic-language region in northeastern France, bordering Germany and Luxembourg, known for its mixed Franco-German cultural heritage.
  • E. Breton
    Breton is a Celtic language spoken primarily in Brittany, France, known for its close relation to Cornish and Welsh.
  • 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_69a4939e889c8190ac148b3ac1a7f90b completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b2cc85a08190bc8186eb9ed1fa38 completed March 1, 2026, 9:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69a7c73b3a848190859df2eed9a21fc5 completed March 4, 2026, 5:46 a.m.
Created at: March 1, 2026, 7:39 p.m.