Triple
T25823172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poljane Valley subdialect |
E650453
|
entity |
| Predicate | hasAccentuation |
P114080
|
FINISHED |
| Object | Upper Carniolan-type accentuation |
—
|
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: Upper Carniolan-type accentuation | Statement: [Poljane Valley subdialect, hasAccentuation, Upper Carniolan-type accentuation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccentuation Context triple: [Poljane Valley subdialect, hasAccentuation, Upper Carniolan-type accentuation]
-
A.
hasAccent
Indicates that an entity speaks with or possesses a particular accent or distinctive pronunciation style.
-
B.
hasAccentFunction
Indicates that one element serves as an accent or emphasis function in relation to another element within a structure or context.
-
C.
hasSpellingWithAccent
Indicates that one form of a word or name is spelled using accented characters compared to another form.
-
D.
hasAccentPosition
Indicates the position within a word or phrase where the primary accent or stress is placed.
-
E.
hasAccentSystem
chosen
Indicates that an entity employs or is characterized by a particular system or pattern of accents (e.g., in language, music, or typography).
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 22, 2026, 7:31 a.m.