Triple
T24839701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chakavian dialect |
E621580
|
entity |
| Predicate | oneOfMainDialectsOf |
P157399
|
FINISHED |
| Object | Croatian language |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Croatian language | Statement: [Chakavian dialect, oneOfMainDialectsOf, Croatian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfMainDialectsOf Context triple: [Chakavian dialect, oneOfMainDialectsOf, Croatian language]
-
A.
majorDialectOf
Indicates that one dialect is the primary or most prominent dialect associated with a particular language or region.
-
B.
dominantDialect
Indicates that one dialect is the primary or most influential form of a language within a particular context or region.
-
C.
consideredDialectOf
Indicates that one language variety is regarded as a dialect of another language or linguistic standard.
-
D.
hasNumberOfDialects
Indicates the relationship between a language (or linguistic entity) and the count of distinct dialects it possesses.
-
E.
notableDialect
Indicates that an entity is recognized for having a distinct or noteworthy dialect associated with it.
- F. None of above. chosen
Provenance (4 batches)
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. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f4303fad6c8190844f069164f0904d |
completed | May 1, 2026, 4:46 a.m. |
Created at: April 18, 2026, 5:18 a.m.