Triple
T4240646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayin |
E95403
|
entity |
| Predicate | representsSoundTraditionally |
P31759
|
FINISHED |
| Object | voiced pharyngeal fricative |
—
|
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: voiced pharyngeal fricative | Statement: [Ayin, representsSoundTraditionally, voiced pharyngeal fricative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsSoundTraditionally Context triple: [Ayin, representsSoundTraditionally, voiced pharyngeal fricative]
-
A.
depictsSound
chosen
Indicates that one entity visually represents or portrays the sound produced by another entity.
-
B.
speechTradition
Indicates a relationship where an entity is associated with, follows, or participates in a particular established way or tradition of speaking or oral expression.
-
C.
hasPhonologicalBasisFor
Indicates that one entity serves as the phonological source, motivation, or foundation for another entity.
-
D.
signatureSound
Indicates that something has a distinctive, characteristic sound that uniquely identifies it.
-
E.
followsSoundOf
Indicates that one entity moves or directs its attention by tracking the source or direction of a sound produced by another entity.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e87c9d88190a093b1289df5b974 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.