Triple

T16906775
Position Surface form Disambiguated ID Type / Status
Subject Hebrew letter Ayin E424583 entity
Predicate hasTraditionalPronunciation P103348 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: [Hebrew letter Ayin, hasTraditionalPronunciation, voiced pharyngeal fricative]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTraditionalPronunciation
Context triple: [Hebrew letter Ayin, hasTraditionalPronunciation, voiced pharyngeal fricative]
  • A. hasTraditionalDialect
    Indicates that an entity possesses or is associated with a traditional form or variety of a language or dialect.
  • B. hasStandardPronunciationBasedOn
    Indicates that one entity’s standard or canonical pronunciation is determined or derived from another entity’s pronunciation.
  • C. hasPronunciationInformation chosen
    Indicates that there is available information describing how something is pronounced.
  • D. hasPronunciationDifferenceFrom
    Indicates that two linguistic items differ in how they are pronounced.
  • E. hasTraditionalName
    Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
  • 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.