Triple
T29258395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wèi |
E741767
|
entity |
| Predicate | hasFinalVowel |
P194853
|
FINISHED |
| Object | /ei/ |
—
|
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: /ei/ | Statement: [Wèi, hasFinalVowel, /ei/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalVowel Context triple: [Wèi, hasFinalVowel, /ei/]
-
A.
hasFinalSyllable
Indicates that one entity possesses or ends with a specific final syllable represented by the other entity.
-
B.
usesFinalConsonants
Indicates that an entity employs or contains consonant sounds in final position, such as at the end of a word, syllable, or phonological unit.
-
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.
hasDependentVowels
Indicates that a writing system or script uses vowel signs that are attached to or depend on consonant characters rather than standing alone as independent letters.
-
E.
hasNasalVowels
Indicates that the subject language or phonological system includes vowels that are produced with nasal airflow (nasalized vowels).
- F. None of above. chosen
Provenance (4 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
| PDg | Predicate description generation | batch_69fd8ccaee848190acd59d7d643ad062 |
completed | May 8, 2026, 7:12 a.m. |
Created at: April 28, 2026, 12:39 p.m.