Triple

T30383823
Position Surface form Disambiguated ID Type / Status
Subject Sony WH-CH520 E772895 entity
Predicate microphoneType P22669 FINISHED
Object built-in electret or MEMS mic (typical for this class) 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: built-in electret or MEMS mic (typical for this class) | Statement: [Sony WH-CH520, microphoneType, built-in electret or MEMS mic (typical for this class)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: microphoneType
Context triple: [Sony WH-CH520, microphoneType, built-in electret or MEMS mic (typical for this class)]
  • A. hasMicrophones chosen
    Indicates that one entity possesses, includes, or is equipped with one or more microphones.
  • B. recordingType
    Indicates the specific kind or category of recording associated with an entity (e.g., audio, video, live, studio, etc.).
  • C. hasSpeakerType
    Indicates that an entity functions in a particular role or category as a speaker (e.g., narrator, character, announcer) within a given context.
  • D. audioJackType
    Indicates the specific kind or standard of audio jack interface used or supported in the relationship.
  • E. headphoneType
    Indicates the specific kind or category of headphones associated with an entity (e.g., in-ear, over-ear, wireless).
  • 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_69f2248e3444819081b05712dc6873de completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6851c44108190822e8d70e1114e09 completed May 2, 2026, 11:13 p.m.
PD Predicate disambiguation batch_69f67e40af9881908de3a4aa15f70a83 completed May 2, 2026, 10:44 p.m.
Created at: April 29, 2026, 8:01 p.m.