Triple
T20594655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audio Fidelity Records |
E506019
|
entity |
| Predicate | soundTechnology |
P3514
|
FINISHED |
| Object | high fidelity |
—
|
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: high fidelity | Statement: [Audio Fidelity Records, soundTechnology, high fidelity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundTechnology Context triple: [Audio Fidelity Records, soundTechnology, high fidelity]
-
A.
soundHardware
Indicates that an entity is associated with, uses, or provides sound-related hardware components or capabilities.
-
B.
soundEngine
Indicates that one entity functions as or provides the sound engine (audio processing or synthesis system) used by another entity.
-
C.
soundReproductionMethod
chosen
Indicates the method or technique used to reproduce or play back sound.
-
D.
audioChip
Indicates that one entity functions as, or contains, an audio processing chip in relation to another entity.
-
E.
soundEngineering
Indicates the relationship in which an entity designs, manipulates, or manages audio elements and acoustics for recording, production, or live sound.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a97e3a7c8190b0b4604aaf40564b |
completed | April 20, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.