Triple
T19451222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluetooth A2DP |
E486617
|
entity |
| Predicate | transmitsFrom |
P4594
|
FINISHED |
| Object | audio source device |
—
|
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: audio source device | Statement: [Bluetooth A2DP, transmitsFrom, audio source device]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmitsFrom Context triple: [Bluetooth A2DP, transmitsFrom, audio source device]
-
A.
transmittedFrom
chosen
Indicates that something (such as information, a signal, or a disease) has been passed or conveyed from one source entity to another.
-
B.
isTransmittedBy
Indicates that something (such as information, a signal, or a disease) is passed or conveyed from one entity to another through a specified agent or medium.
-
C.
transmittedIn
Indicates that something (such as information, a signal, or a disease) is passed or conveyed within or through a particular medium, environment, or context.
-
D.
communicatesFrom
Indicates that information, messages, or signals are sent or expressed from one entity to another.
-
E.
laterTransmission
Indicates that one transmission event occurs after another in time.
- 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.