Triple
T19451230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluetooth A2DP |
E486617
|
entity |
| Predicate | audioDirection |
P25438
|
FINISHED |
| Object | unidirectional |
—
|
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: unidirectional | Statement: [Bluetooth A2DP, audioDirection, unidirectional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioDirection Context triple: [Bluetooth A2DP, audioDirection, unidirectional]
-
A.
mediaDirection
chosen
Indicates the direction or flow of media transmission between entities, such as who is sending and who is receiving the media.
-
B.
audioChannelsType
Indicates the type or configuration of audio channels used in an audio signal or recording (e.g., mono, stereo, surround).
-
C.
audioChannels
Indicates the number or configuration of distinct audio signal paths (such as mono, stereo, or surround) used in a recording, transmission, or playback.
-
D.
speakerPosition
Indicates the spatial or contextual location of a speaker relative to other entities or a reference frame during an utterance or event.
-
E.
connectionDirection
Indicates the directional flow or orientation of a connection from one entity to another.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338db7c081908793f23592ebef6b |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.