Triple
T31997358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balangiri dialect |
E817028
|
entity |
| Predicate | hasRegionSpecificPronunciation |
P32680
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Balangiri dialect, hasRegionSpecificPronunciation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionSpecificPronunciation Context triple: [Balangiri dialect, hasRegionSpecificPronunciation, true]
-
A.
hasPronunciationDifferenceFrom
Indicates that two linguistic items differ in how they are pronounced.
-
B.
hasStandardPronunciationBasedOn
Indicates that one entity’s standard or canonical pronunciation is determined or derived from another entity’s pronunciation.
-
C.
isMorePronouncedIn
Indicates that a particular feature, quality, or effect appears with greater intensity or prominence in one context, entity, or condition than in another.
-
D.
hasRegionalVariationsIn
chosen
Indicates that something exhibits different forms, versions, or characteristics depending on the geographic region.
-
E.
correctPronunciation
Indicates that one entity provides the accurate or standard way to pronounce another entity (such as a word or name).
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01bb9c33cc8190a95ba124d97edf99 |
completed | May 11, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_6a01bb6772148190a243d1141ad0a237 |
completed | May 11, 2026, 11:20 a.m. |
Created at: May 1, 2026, 12:14 a.m.