Triple
T24839680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chakavian dialect |
E621580
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Croatian dialect |
C21291
|
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: Croatian dialect Context triple: [Chakavian dialect, instanceOf, Croatian dialect]
-
A.
dialect of Croatian
chosen
A dialect of Croatian is a regional or social variety of the Croatian language characterized by distinct phonological, morphological, syntactic, and lexical features that differentiate it from the standard language and other Croatian dialects.
-
B.
Kajkavian
Kajkavian is a South Slavic dialect (often considered a dialect of Croatian) characterized by its use of the interrogative pronoun "kaj," distinct phonological and grammatical features, and a historical literary tradition.
-
C.
Slovene dialect
A Slovene dialect is a regional or social variety of the Slovene language characterized by distinct phonological, morphological, syntactic, and lexical features that differentiate it from standard Slovene and other Slovene dialects.
-
D.
Slovene dialect group
A Slovene dialect group is a classification of closely related regional varieties of the Slovene language that share common phonological, morphological, syntactic, and lexical features.
-
E.
standard variety of Serbo-Croatian
The standard variety of Serbo-Croatian is the codified, prestige form of the Serbo-Croatian language used in formal communication, education, media, and official contexts across Bosnia and Herzegovina, Croatia, Montenegro, and Serbia, based primarily on the Shtokavian dialect.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:18 a.m.