Triple
T16906778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebrew letter Ayin |
E424583
|
entity |
| Predicate | hasVoicing |
P125166
|
FINISHED |
| Object | voiced |
—
|
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 | Statement: [Hebrew letter Ayin, hasVoicing, voiced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVoicing Context triple: [Hebrew letter Ayin, hasVoicing, voiced]
-
A.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
-
B.
hasVoices
Indicates that an entity possesses or includes one or more vocal parts, voice tracks, or spoken/sung voice elements.
-
C.
hasVoiceActing
Indicates that one entity provides voice performance for a character, role, or work associated with another entity.
-
D.
hasInnerVoice
Indicates that an entity possesses an internal monologue or subjective stream of thoughts not externally expressed.
-
E.
hasVocalForces
Indicates that an entity involves or employs vocal performers or vocal parts as a contributing force.
- 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_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. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:30 a.m.