Triple

T29388137
Position Surface form Disambiguated ID Type / Status
Subject Bluetooth Core Specification E745304 entity
Predicate specifies P773 FINISHED
Object Bluetooth advertising channels
Bluetooth advertising channels are specific radio frequencies used by Bluetooth devices to broadcast discovery and connection information to nearby devices.
E745304 NE 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: Bluetooth advertising channels | Statement: [Bluetooth Core Specification, specifies, Bluetooth advertising channels]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Bluetooth advertising channels
Triple: [Bluetooth Core Specification, specifies, Bluetooth advertising channels]
Generated description
Bluetooth advertising channels are specific radio frequencies used by Bluetooth devices to broadcast discovery and connection information to nearby devices.

Provenance (5 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_69f0a79cfd5481909b4dde750cb8d2c6 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f669d44b7c8190a79e108c68a7077a completed May 2, 2026, 9:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25c1133ad48190bbd371e89b52bc1f completed June 7, 2026, 7:05 p.m.
NEDg Description generation batch_6a25ccabb11c8190b4085aab38ffd0da completed June 7, 2026, 7:55 p.m.
NED2 Entity disambiguation (via description) batch_6a25cd411cd8819082ca2e7fceae0e33 completed June 7, 2026, 7:57 p.m.
Created at: April 28, 2026, 2:40 p.m.