Triple
T32291360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caló |
E824974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iberian Romani lect |
C23958
|
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: Iberian Romani lect Context triple: [Caló, instanceOf, Iberian Romani lect]
-
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.
Sardinian-related lect
A Sardinian-related lect is a variety of speech (language or dialect) that is historically and structurally connected to the Sardinian language, sharing core linguistic features while differing in geography, usage, or standardization.
-
C.
dictionary of Romance languages
A dictionary of Romance languages is a reference work that lists words and their meanings, translations, and usage across one or more languages derived from Latin, such as Spanish, French, Italian, Portuguese, and Romanian.
-
D.
para-Romani variety
chosen
A para-Romani variety is a mixed language in which Romani-derived vocabulary is embedded into the grammatical structure of a surrounding majority language, typically used as an in-group code by Romani or Romani-associated communities.
-
E.
Spanish language corpus
A Spanish language corpus is a structured, large-scale collection of Spanish texts (written and/or spoken) compiled to support linguistic analysis, language research, and natural language processing applications.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:44 a.m.