Triple
T5384964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eonavian language |
E120180
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Astur-Leonese language variety |
C5912
|
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: Astur-Leonese language variety Context triple: [Eonavian language, instanceOf, Astur-Leonese language variety]
-
A.
Astur-Leonese language
The Astur-Leonese language is a Romance language continuum spoken primarily in Asturias, León, and surrounding regions of northwestern Spain, characterized by its own distinct phonological, lexical, and grammatical features separate from Spanish and Galician-Portuguese.
-
B.
variety of the Spanish language
A variety of the Spanish language is a distinct form of Spanish characterized by specific phonological, grammatical, lexical, and pragmatic features associated with a particular geographic region, social group, or communicative context.
-
C.
Romance language variety
chosen
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.
-
D.
Occitan dialect
An Occitan dialect is a regional variety of the Occitan language, characterized by distinct phonological, lexical, and grammatical features shaped by local history and geography within southern France and neighboring areas.
-
E.
Costanoan language
The Costanoan language is a group of closely related, now mostly extinct, Native American languages once spoken by the Ohlone people along the central coast of California.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
Created at: March 20, 2026, 2:03 p.m.