Triple
T4091156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbian language |
E87705
|
entity |
| Predicate | basedOnDialectGroup |
P1254
|
FINISHED |
| Object | Shtokavian dialect |
—
|
LITERAL FINISHED |
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: Shtokavian dialect | Statement: [Serbian language, basedOnDialectGroup, Shtokavian dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnDialectGroup Context triple: [Serbian language, basedOnDialectGroup, Shtokavian dialect]
-
A.
isBasedOnDialect
Indicates that something (such as a language variety, system, or representation) is derived from, structured around, or primarily influenced by a particular dialect.
-
B.
focusesOnDialect
Indicates that the subject’s attention, work, or activity is specifically directed toward a particular dialect or set of dialects.
-
C.
hasMajorDialectGroup
chosen
Indicates that an entity (typically a language) is associated with a primary or major dialect group to which it belongs.
-
D.
usesDialect
Indicates that one entity communicates or expresses itself using the specific dialect associated with another entity.
-
E.
hasDialectsIn
Indicates that a language or linguistic variety possesses distinct dialects that are used or found within a specified region or context.
- F. None of above.
Provenance (3 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcac77788190a5e934fe7c46a1fa |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.