Triple
T2455924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navajo language |
E54419
|
entity |
| Predicate | hasNumberOfTones |
P4432
|
FINISHED |
| Object | 2 or more lexical tones |
—
|
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: 2 or more lexical tones | Statement: [Navajo language, hasNumberOfTones, 2 or more lexical tones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfTones Context triple: [Navajo language, hasNumberOfTones, 2 or more lexical tones]
-
A.
representsNumberOfTones
chosen
Indicates that one entity specifies or encodes the number of tones associated with another entity.
-
B.
hasPhonemicTone
Indicates that a language, word, or syllable uses pitch differences (tones) as phonemic contrasts that can change meaning.
-
C.
hasPhoneme
Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
-
D.
hasPhonemeInventory
Indicates that an entity possesses a specific set or system of distinct speech sounds (phonemes) used in its language.
-
E.
hasConsonantPhonemes
Indicates that an entity possesses or includes one or more consonant phonemes in its phonological system.
- 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0aed2688190a18fe66b98d80e0b |
completed | March 7, 2026, 7:15 a.m. |
Created at: March 6, 2026, 9:44 p.m.