Triple
T15254812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N96 |
E364617
|
entity |
| Predicate | bluetoothFeatures |
P116731
|
FINISHED |
| Object | A2DP |
—
|
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: A2DP | Statement: [Nokia N96, bluetoothFeatures, A2DP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bluetoothFeatures Context triple: [Nokia N96, bluetoothFeatures, A2DP]
-
A.
hasBluetooth
Indicates that one entity is equipped with or supports Bluetooth connectivity.
-
B.
supportsBluetoothCodec
chosen
Indicates that one entity is capable of using or is compatible with a specified Bluetooth audio codec in its operation or communication.
-
C.
connectivityFeatures
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
-
D.
usbFeatures
Indicates that there exists a relationship specifying the USB-related capabilities or characteristics supported by an entity.
-
E.
eraCharacteristic
Indicates that a particular quality, feature, or attribute is characteristic of, or typically associated with, a given historical or temporal era.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f8cb308190933c4478aa096e24 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.