Triple
T2980892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleph |
E80506
|
entity |
| Predicate | phoneticValue |
P44421
|
FINISHED |
| Object | glottal stop |
—
|
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: glottal stop | Statement: [Aleph, phoneticValue, glottal stop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phoneticValue Context triple: [Aleph, phoneticValue, glottal stop]
-
A.
isPhonetic
Indicates that one entity represents the phonetic (sound-based) form or pronunciation of another entity.
-
B.
phoneticComponents
Indicates that one entity serves as a phonetic component or contributes to the pronunciation of another entity.
-
C.
phoneticProcess
Indicates a relationship where one sound or sequence of sounds undergoes a systematic phonetic change or transformation in a particular linguistic context.
-
D.
hasPhoneme
Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
-
E.
hasPhonemicTone
Indicates that a language, word, or syllable uses pitch differences (tones) as phonemic contrasts that can change meaning.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999e91788190a2d430dd0600a660 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:58 p.m.