Triple
T12754751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia E60 |
E304827
|
entity |
| Predicate | supportsBluetoothProfile |
P39529
|
FINISHED |
| Object | Bluetooth 1.x |
—
|
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: Bluetooth 1.x | Statement: [Nokia E60, supportsBluetoothProfile, Bluetooth 1.x]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBluetoothProfile Context triple: [Nokia E60, supportsBluetoothProfile, Bluetooth 1.x]
-
A.
hasBluetooth
chosen
Indicates that one entity is equipped with or supports Bluetooth connectivity.
-
B.
supportsTethering
Indicates that one entity enables or allows another entity to share its network connection with additional devices (i.e., provides tethering capability).
-
C.
supportsInfraredConnectivity
Indicates that one entity provides or enables infrared-based communication or data transfer capabilities for another entity.
-
D.
wirelessSupportIntroduced
Indicates that support for wireless functionality was added or became available for the first time.
-
E.
supportsLTE
Indicates that one entity provides compatibility with or functionality for LTE (Long-Term Evolution) cellular communication for 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.