Triple
T29388227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluetooth L2CAP |
E745306
|
entity |
| Predicate | hasControlSignaling |
P64026
|
FINISHED |
| Object | L2CAP signaling channel |
—
|
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: L2CAP signaling channel | Statement: [Bluetooth L2CAP, hasControlSignaling, L2CAP signaling channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlSignaling Context triple: [Bluetooth L2CAP, hasControlSignaling, L2CAP signaling channel]
-
A.
usesSignalingChannel
chosen
Indicates that one entity communicates or exchanges information with another through a specific signaling channel or medium.
-
B.
usesSignaling
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
-
C.
usesBalancedSignaling
Indicates that an entity employs a signaling strategy in which opposing or complementary signals are used in a coordinated, proportionate way to maintain balance in communication or control.
-
D.
signalingMode
Indicates the method or mechanism by which one entity communicates or transmits signals to another.
-
E.
compatibleWithSignaling
Indicates that one entity can correctly interpret, process, or operate using the signaling mechanisms, protocols, or formats employed by another entity.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a005e8a2f7c819085bfc6f04b866d87 |
completed | May 10, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_6a005de82ef08190a015b385d1d3443c |
completed | May 10, 2026, 10:28 a.m. |
Created at: April 28, 2026, 2:40 p.m.