Triple
T6473664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazahua |
E146014
|
entity |
| Predicate | hasPhonemeInventorySize |
P65631
|
FINISHED |
| Object | large consonant inventory |
—
|
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: large consonant inventory | Statement: [Mazahua, hasPhonemeInventorySize, large consonant inventory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhonemeInventorySize Context triple: [Mazahua, hasPhonemeInventorySize, large consonant inventory]
-
A.
hasPhonemeInventory
Indicates that an entity possesses a specific set or system of distinct speech sounds (phonemes) used in its language.
-
B.
phonemeInventorySize
chosen
Indicates the number of distinct phonemes present in a language’s sound system.
-
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.
hasPhonemicVowels
Indicates that a language or linguistic system distinguishes vowel sounds as separate phonemes that can change word meaning.
-
E.
hasPhonologicalParameters
Indicates that an entity is associated with specific phonological features or parameters that characterize its sound structure.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a32c0188190bcb3c35fc1d796a6 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:50 p.m.