Triple

T30784965
Position Surface form Disambiguated ID Type / Status
Subject Colonial French E783932 entity
Predicate instanceOf P0 FINISHED
Object historical variety of the French language C1171 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: historical variety of the French language
Context triple: [Colonial French, instanceOf, historical variety of the French language]
  • A. Romance language variety
    A Romance language variety is a specific form or dialect of a Romance language, distinguished by its unique phonological, grammatical, and lexical features within the broader Romance language family.
  • B. regional variety of the Breton language
    A regional variety of the Breton language is a geographically defined form of Breton characterized by distinct phonological, lexical, and sometimes grammatical features that differentiate it from other Breton dialects.
  • C. classical language variety
    A classical language variety is a historically prestigious, standardized form of a language, typically preserved in literature and formal contexts, that differs from its modern spoken descendants.
  • D. Oïl language chosen
    An Oïl language is any of a group of closely related Romance languages and dialects historically spoken in northern France, Belgium, and the Channel Islands, characterized by the use of "oïl" (modern "oui") for "yes."
  • E. regional variety of Acadian French
    A regional variety of Acadian French is a localized form of the French language spoken by Acadian communities, characterized by distinct phonological, lexical, and syntactic features shaped by historical isolation and contact with other languages.
  • F. None of above.

Provenance (1 batch)

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_69f224b213c8819083886073f90b647e completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 8:41 p.m.