Triple
T3981812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CORPES XXI corpus |
E85774
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish language corpus |
C15287
|
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: Spanish language corpus Context triple: [CORPES XXI corpus, instanceOf, Spanish language corpus]
-
A.
dictionary of the Spanish language
A dictionary of the Spanish language is a reference work that systematically lists Spanish words and expressions, providing their meanings, grammatical information, usage notes, and often etymology.
-
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.
Spanish-language dictionary
A Spanish-language dictionary is a reference work that lists Spanish words and expressions, providing their meanings, grammatical information, and often pronunciation and usage examples.
-
D.
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.
-
E.
documentation corpus
A documentation corpus is a structured collection of written materials, such as manuals, guides, and reference texts, compiled to provide comprehensive information and support for a specific domain, product, or system.
- F. None of above. chosen
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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:33 p.m.