Triple
T19471767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boehkhʼul |
E487138
|
entity |
| Predicate | hasStandardPronunciation |
P69033
|
FINISHED |
| Object | Khunzakh-based pronunciation norm |
—
|
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: Khunzakh-based pronunciation norm | Statement: [Boehkhʼul, hasStandardPronunciation, Khunzakh-based pronunciation norm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardPronunciation Context triple: [Boehkhʼul, hasStandardPronunciation, Khunzakh-based pronunciation norm]
-
A.
hasStandardPronunciationBasedOn
Indicates that one entity’s standard or canonical pronunciation is determined or derived from another entity’s pronunciation.
-
B.
hasPhonologicalStandard
chosen
Indicates that one entity serves as the accepted or prescribed phonological norm or standard for the pronunciation system of another entity.
-
C.
hasPronunciationInformation
Indicates that there is available information describing how something is pronounced.
-
D.
pronunciationLanguage
Indicates the language in which the pronunciation of an entity (such as a word or name) is given.
-
E.
hasSpokenStandard
Indicates that an entity has spoken using a recognized standard form of a language (e.g., standard dialect or official register).
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e8d9188190a4939f03bad89add |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.