Triple
T4240648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayin |
E95403
|
entity |
| Predicate | representsSoundInModernHebrew |
P54886
|
FINISHED |
| Object | silent consonant |
—
|
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: silent consonant | Statement: [Ayin, representsSoundInModernHebrew, silent consonant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsSoundInModernHebrew Context triple: [Ayin, representsSoundInModernHebrew, silent consonant]
-
A.
representsNumberInHebrewNumerals
Indicates that one entity is used to represent the numerical value of another entity using Hebrew numeral notation.
-
B.
hasNameInHebrew
Indicates that an entity is associated with a specific name expressed in the Hebrew language.
-
C.
hasPhonologicalBasisFor
Indicates that one entity serves as the phonological source, motivation, or foundation for another entity.
-
D.
depictsSound
Indicates that one entity visually represents or portrays the sound produced by another entity.
-
E.
numericalValueHebrewGematria
Indicates that a numerical value is assigned to text based on Hebrew gematria, where Hebrew letters correspond to specific numbers and their sum yields the value.
- 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_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. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:05 p.m.