Triple

T1347113
Position Surface form Disambiguated ID Type / Status
Subject Avignon E28595 entity
Predicate traditionalLanguage P6149 FINISHED
Object Occitan E14615 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: Occitan | Statement: [Avignon, traditionalLanguage, Occitan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Occitan
Context triple: [Avignon, traditionalLanguage, Occitan]
  • A. Occitan chosen
    Occitan is a Romance language historically spoken in southern France and neighboring regions, known for its rich medieval literary tradition and close relation to Catalan.
  • B. Niçard Occitan
    Niçard Occitan is a Romance variety of the Occitan language traditionally spoken in and around the city of Nice in southeastern France.
  • C. 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.
  • D. Corsican language
    Corsican language is a Romance language closely related to Italian, traditionally spoken on the island of Corsica and parts of northern Sardinia.
  • E. Piemontèis
    Piemontèis is the native name for the Piedmontese language, a Romance language spoken primarily in Italy’s Piedmont 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_69a49854eb3481908c7d56b2e449a290 completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c2406c488190b2c04d54d9c5e94c completed March 1, 2026, 10:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69acc639201c81908ed9c9ac37cd358f completed March 8, 2026, 12:43 a.m.
Created at: March 1, 2026, 7:56 p.m.