Triple
T12021018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 3310 (2017) |
E286147
|
entity |
| Predicate | supports2GNetworks |
P68289
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nokia 3310 (2017), supports2GNetworks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supports2GNetworks Context triple: [Nokia 3310 (2017), supports2GNetworks, yes]
-
A.
supportsSingleFrequencyNetworks
Indicates that an entity enables or is compatible with operating in single frequency networks, where multiple transmitters use the same frequency to provide coordinated coverage.
-
B.
supportsNetworkingModel
Indicates that one entity provides compatibility with, or implementation of, a specified networking model for another entity.
-
C.
supportsWiFiStandard
Indicates that one entity is compatible with and able to operate using a specified Wi-Fi communication standard defined by another entity.
-
D.
frequencyBandSupported
chosen
Indicates that an entity supports operation or functionality within a specified frequency band.
-
E.
supportsTethering
Indicates that one entity enables or allows another entity to share its network connection with additional devices (i.e., provides tethering capability).
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.