Triple
T19451237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluetooth A2DP |
E486617
|
entity |
| Predicate | supportsCodec |
P203
|
FINISHED |
| Object | LDAC |
—
|
NE NERFINISHED |
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: LDAC | Statement: [Bluetooth A2DP, supportsCodec, LDAC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LDAC Context triple: [Bluetooth A2DP, supportsCodec, LDAC]
-
A.
LDAC
chosen
LDAC is a high-resolution Bluetooth audio codec developed by Sony that enables wireless transmission of higher-quality audio than standard codecs like SBC.
-
B.
LHDC
LHDC is the ICAO airport code assigned to Debrecen International Airport in Hungary.
-
C.
aptX
aptX is an audio codec designed to deliver higher-quality, low-latency wireless sound, commonly used over Bluetooth connections for music and media streaming.
-
D.
Advanced Audio Distribution Profile
Advanced Audio Distribution Profile is a Bluetooth profile designed for high-quality wireless audio streaming from a source device to compatible audio receivers such as headphones or speakers.
-
E.
ER-AAC ELD
ER-AAC ELD is a low-delay, high-efficiency audio coding profile of Advanced Audio Coding designed for real-time communication and streaming applications.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338db7c081908793f23592ebef6b |
completed | April 20, 2026, 2:09 p.m. |
Created at: April 10, 2026, 1:38 p.m.