Triple
T30723712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurdan |
E782218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ibero-Romance dialect |
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: Ibero-Romance dialect Context triple: [Hurdan, instanceOf, Ibero-Romance dialect]
-
A.
Caribbean Spanish dialect
Caribbean Spanish dialect is a regional variety of Spanish spoken in Caribbean nations and coastal areas, characterized by features such as syllable-final consonant weakening, rapid rhythm, and distinctive intonation patterns influenced by African, Indigenous, and European languages.
-
B.
Basque dialect
A Basque dialect is a regional or social variety of the Basque language characterized by distinct phonological, lexical, and grammatical features used by a specific speech community.
-
C.
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.
-
D.
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.
-
E.
Sardinian dialect
Sardinian dialect is a regional variety of the Sardinian language, characterized by distinct phonetic, lexical, and grammatical features that vary across different areas of the island of Sardinia.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:36 p.m.