Triple

T29391968
Position Surface form Disambiguated ID Type / Status
Subject nRF5 SDK E745387 entity
Predicate supports P516 FINISHED
Object Bluetooth Low Energy
Bluetooth Low Energy is a power-efficient wireless communication technology designed for short-range data exchange, commonly used in IoT devices, wearables, and mobile accessories.
E1886114 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 Low Energy | Statement: [nRF5 SDK, supports, Bluetooth Low Energy]
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 Low Energy
Triple: [nRF5 SDK, supports, Bluetooth Low Energy]
Generated description
Bluetooth Low Energy is a power-efficient wireless communication technology designed for short-range data exchange, commonly used in IoT devices, wearables, and mobile accessories.

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_69f0a79dfabc81908755382ee47791e2 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f669ff3b2081909ecfc701841c6532 completed May 2, 2026, 9:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a26e5d156788190846036785cbad129 completed June 8, 2026, 3:54 p.m.
NEDg Description generation batch_6a26e6bbf9108190807bfaf6cf1726b2 completed June 8, 2026, 3:58 p.m.
NED2 Entity disambiguation (via description) batch_6a26e7de09548190adfb56b57b826c9e completed June 8, 2026, 4:03 p.m.
Created at: April 28, 2026, 2:43 p.m.