Triple
T5440863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornish |
E122128
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Southwestern Brittonic language |
C315
|
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: Southwestern Brittonic language Context triple: [Cornish, instanceOf, Southwestern Brittonic language]
-
A.
Celtic language
chosen
A Celtic language is a member of the Indo-European language family historically spoken in Western Europe, characterized by shared phonological, grammatical, and lexical features found in branches such as Goidelic (e.g., Irish, Scottish Gaelic) and Brittonic (e.g., Welsh, Breton).
-
B.
Gallo-Italic language
A Gallo-Italic language is a member of a group of Romance languages spoken primarily in northern Italy and parts of Switzerland, characterized by features intermediate between Gallo-Romance (like French) and Italo-Romance (like standard Italian).
-
C.
Goidelic language
A Goidelic language is a member of the Celtic language family originating in Ireland and Scotland, including Irish, Scottish Gaelic, and Manx.
-
D.
West Germanic language
A West Germanic language is a member of the Germanic branch of the Indo-European language family that evolved in western and central Europe, including languages such as English, German, and Dutch.
-
E.
Paleo-European language
A Paleo-European language is a hypothesized pre-Indo-European language or group of languages once spoken in prehistoric Europe, known primarily through substratum influences, place names, and limited archaeological and linguistic reconstruction.
- 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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:07 p.m.