Triple
T24839727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varaždin Kajkavian |
E621581
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kajkavian dialect variety |
C21292
|
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: Kajkavian dialect variety Context triple: [Varaždin Kajkavian, instanceOf, Kajkavian dialect variety]
-
A.
Kajkavian
chosen
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.
-
B.
dialect of Croatian
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.
-
C.
Balkan Slavic dialects
Balkan Slavic dialects are a group of South Slavic vernaculars spoken in the Balkan Peninsula that share distinctive grammatical and phonological features shaped by intense contact with neighboring Balkan languages.
-
D.
regional variety of Lombard
A regional variety of Lombard is a specific form of the Lombard language spoken in a particular geographic area, characterized by distinct phonological, lexical, and syntactic features.
-
E.
Slavic dialect
A Slavic dialect is a regional or social variety of a Slavic language characterized by distinct phonological, grammatical, and lexical features that differentiate it from the standard language and other dialects.
- 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.