Triple
T4411067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawaiian alphabet |
E94853
|
entity |
| Predicate | hasFiveVowelSystem |
P22962
|
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: [Hawaiian alphabet, hasFiveVowelSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFiveVowelSystem Context triple: [Hawaiian alphabet, hasFiveVowelSystem, true]
-
A.
hasVowelSystem
chosen
Indicates that an entity possesses a particular system or pattern of vowel sounds (a structured set of vowel phonemes or contrasts).
-
B.
hasVowelNotationSystem
Indicates that a writing or transcription system for a language includes a method for explicitly representing vowel sounds.
-
C.
hasVowelHarmony
Indicates that the phonological vowels in a word or morpheme conform to a systematic harmony pattern (e.g., all front or all back vowels) according to the language’s vowel harmony rules.
-
D.
hasVowelFeature
Indicates that an entity possesses a specific vowel-related phonological or articulatory feature.
-
E.
hasVowelLengthContrast
Indicates that a language distinguishes word meanings based on differences in the length (duration) of vowel sounds.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e4c58c8190b4190aad3095a1dd |
completed | March 13, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.