Triple
T30726749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UWB |
E782296
|
entity |
| Predicate | hasAdvantageOverBluetoothLowEnergy |
P186469
|
FINISHED |
| Object | higher ranging accuracy |
—
|
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: higher ranging accuracy | Statement: [UWB, hasAdvantageOverBluetoothLowEnergy, higher ranging accuracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdvantageOverBluetoothLowEnergy Context triple: [UWB, hasAdvantageOverBluetoothLowEnergy, higher ranging accuracy]
-
A.
hasBluetooth
Indicates that one entity is equipped with or supports Bluetooth connectivity.
-
B.
supportsBluetoothCodec
Indicates that one entity is capable of using or is compatible with a specified Bluetooth audio codec in its operation or communication.
-
C.
hasCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
D.
eraCharacteristic
Indicates that a particular quality, feature, or attribute is characteristic of, or typically associated with, a given historical or temporal era.
-
E.
canBondWith
Indicates that one entity has the capability or compatibility to form a bond or connection with another entity.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: April 29, 2026, 8:37 p.m.