Triple
T19644616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayre Acoustics |
E471640
|
entity |
| Predicate | audioFormatSupport |
P85613
|
FINISHED |
| Object | digital audio |
—
|
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: digital audio | Statement: [Ayre Acoustics, audioFormatSupport, digital audio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioFormatSupport Context triple: [Ayre Acoustics, audioFormatSupport, digital audio]
-
A.
audioFormatSupported
chosen
Indicates that a particular audio format is recognized and can be correctly processed or played by a given system or component.
-
B.
audioStandard
Indicates the audio format or specification standard that applies to the associated media or device.
-
C.
supportsAudioQuality
Indicates that one entity provides or is compatible with a specified level or type of audio quality for another entity or context.
-
D.
supportsPCM
Indicates that one entity is capable of handling, processing, or is compatible with PCM (Pulse-Code Modulation) audio data used by another entity.
-
E.
hasPlayFormat
Indicates that something (such as a game, media, or activity) is associated with a particular format or mode in which it is played or experienced.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6412452d481908b6946cad3c411d5 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.