Triple
T14395751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shtokavian dialect |
E356943
|
entity |
| Predicate | hasAccentSystem |
P114080
|
FINISHED |
| Object | pitch accent |
—
|
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: pitch accent | Statement: [Shtokavian dialect, hasAccentSystem, pitch accent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccentSystem Context triple: [Shtokavian dialect, hasAccentSystem, pitch accent]
-
A.
hasAccent
Indicates that an entity speaks with or possesses a particular accent or distinctive pronunciation style.
-
B.
hasAccentPosition
Indicates the position within a word or phrase where the primary accent or stress is placed.
-
C.
usesPhoneticSystem
Indicates that one entity employs or is based on a particular phonetic system for representing or encoding sounds.
-
D.
usesDiacritics
Indicates that the referenced text or linguistic element employs diacritical marks as part of its written form.
-
E.
hasPunctuationSystem
Indicates that an entity possesses or employs a system of punctuation marks for structuring written language.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90826f908190b3969af9b7cf922f |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e08b6c08190bb4c929deab236a6 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:17 a.m.