Triple
T35012776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jel |
E1009974
|
entity |
| Predicate | phoneticCharacteristics |
P29850
|
FINISHED |
| Object | sibilant sounds |
—
|
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: sibilant sounds | Statement: [Jel, phoneticCharacteristics, sibilant sounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phoneticCharacteristics Context triple: [Jel, phoneticCharacteristics, sibilant sounds]
-
A.
phoneticComponents
Indicates that one entity serves as a phonetic component or contributes to the pronunciation of another entity.
-
B.
vocalizationCharacteristic
chosen
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
C.
phoneticValue
Indicates a relationship where a symbol, sign, or written element is associated with the specific sound or sequence of sounds it represents.
-
D.
phoneticPattern
Indicates that two or more linguistic elements share a specific arrangement or sequence of sounds according to a defined phonological structure.
-
E.
hasPhonologicalDescription
Indicates that an entity is associated with a specific representation or description of its sound structure or phonological form.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.