Triple
T29388224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluetooth L2CAP |
E745306
|
entity |
| Predicate | notUsedOver |
P166707
|
FINISHED |
| Object | SCO links in classic Bluetooth |
—
|
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: SCO links in classic Bluetooth | Statement: [Bluetooth L2CAP, notUsedOver, SCO links in classic Bluetooth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notUsedOver Context triple: [Bluetooth L2CAP, notUsedOver, SCO links in classic Bluetooth]
-
A.
notUsedAt
Indicates that a particular entity is not utilized, applied, or active at a specified location, time, or context.
-
B.
notAutomaticallyUsedBy
Indicates that something is not used by another entity in an automatic or default manner and instead requires explicit action or configuration to be used.
-
C.
notReusedFor
Indicates that something is not used again for a subsequent purpose, context, or instance.
-
D.
usedLessIn
Indicates that one entity is used with a lower frequency or intensity compared to another entity.
-
E.
isNotUsedAs
Indicates that one entity does not serve, function, or act in the role or capacity of another specified entity or purpose.
- F. None of above. chosen
Provenance (4 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. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 2:40 p.m.