Triple
T21126755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unified Cornish Revised |
E520577
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | standardized form of Cornish |
C4690
|
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: standardized form of Cornish Context triple: [Unified Cornish Revised, instanceOf, standardized form of Cornish]
-
A.
constructed variety of Cornish
A constructed variety of Cornish is a deliberately planned and standardized form of the Cornish language, created by linguists or language planners to revive, regularize, or adapt it for contemporary use.
-
B.
Gutnish variety
A Gutnish variety is a regional form of the Gutnish language spoken on the island of Gotland and surrounding areas, characterized by distinct phonological, lexical, and grammatical features that differentiate it from standard Swedish and other Scandinavian dialects.
-
C.
standardized form
A standardized form is a pre-designed, uniform document or template used to consistently collect, organize, and process specific types of information across multiple instances or users.
-
D.
standardized language variety
chosen
A standardized language variety is a codified form of a language that has been deliberately regulated and accepted as the norm for public, official, and educational use within a speech community.
-
E.
Cora language variety
Cora language variety refers to any distinct regional, social, or dialectal form of the Cora language as used by different Cora-speaking communities.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:56 p.m.