Triple

T1037046
Position Surface form Disambiguated ID Type / Status
Subject Celtic languages E22386 entity
Predicate includesLanguage P2177 FINISHED
Object Breton E29282 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: Breton | Statement: [Celtic languages, includesLanguage, Breton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Breton
Context triple: [Celtic languages, includesLanguage, Breton]
  • A. Breton chosen
    Breton is a Celtic language spoken primarily in Brittany, France, known for its close relation to Cornish and Welsh.
  • B. Brittany
    Brittany is a historic cultural region in northwest France known for its distinct Celtic heritage, Breton language, rugged coastline, and strong Catholic traditions.
  • C. Jèrriais
    Jèrriais is a Norman Romance language traditionally spoken on the island of Jersey in the Channel Islands.
  • D. Mor Breizh
    Mor Breizh is the Breton name for the English Channel, the arm of the Atlantic Ocean that separates southern England from northern France.
  • E. Auvergnat
    Auvergnat is a variety of the Occitan language traditionally spoken in France’s Auvergne region and surrounding areas.
  • 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_69a493d848848190aed4011b34b2e8d3 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b82a1014819085bfc077e24c9742 completed March 1, 2026, 10:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac3bc378fc8190846d5ffce73371dd completed March 7, 2026, 2:52 p.m.
Created at: March 1, 2026, 7:41 p.m.