Triple
T16906777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebrew letter Ayin |
E424583
|
entity |
| Predicate | hasArticulationManner |
P40501
|
FINISHED |
| Object | 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: fricative | Statement: [Hebrew letter Ayin, hasArticulationManner, fricative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArticulationManner Context triple: [Hebrew letter Ayin, hasArticulationManner, fricative]
-
A.
hasConsonantManner
chosen
Indicates that one sound is related to another by sharing a specific manner of consonant articulation (e.g., stop, fricative, nasal).
-
B.
hasArticulation
Indicates that one entity possesses or exhibits a specific type or structure of articulation in relation to another entity or system.
-
C.
hasArticulationType
Indicates the specific manner or type of connection or joint by which two parts or entities are linked or articulated.
-
D.
usesArticulators
Indicates that an entity performs an action or produces a signal by employing specific speech or movement articulators (e.g., tongue, lips, jaw).
-
E.
placeOfArticulation
Indicates the specific location within the vocal tract where a speech sound is produced.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3ca39f9b08190b15106c6caf895ec |
completed | April 18, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.