Triple
T12969627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia E70 |
E321357
|
entity |
| Predicate | usbStandard |
P85937
|
FINISHED |
| Object | USB 2.0 |
—
|
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: USB 2.0 | Statement: [Nokia E70, usbStandard, USB 2.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usbStandard Context triple: [Nokia E70, usbStandard, USB 2.0]
-
A.
usbFeatures
Indicates that there exists a relationship specifying the USB-related capabilities or characteristics supported by an entity.
-
B.
usbCPortSpecification
Indicates that one entity defines or conforms to the technical specifications of a USB-C port used by another entity.
-
C.
usbCDataTransferSpeed
Indicates the rate at which data can be transmitted over a USB-C connection between devices.
-
D.
hasUSBPort
Indicates that one entity is equipped with or includes a USB port available for connection or data/power transfer.
-
E.
hasUSB2Ports
chosen
Indicates that an entity is equipped with one or more USB 2.0 standard ports.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:34 p.m.