Triple
T18262919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 6280 |
E437406
|
entity |
| Predicate | supports3GData |
P102678
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nokia 6280, supports3GData, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supports3GData Context triple: [Nokia 6280, supports3GData, true]
-
A.
supports3G
chosen
Indicates that one entity provides or is compatible with 3G mobile network connectivity for another entity or for its operation.
-
B.
supportsGPRS
Indicates that one entity provides or is compatible with GPRS (General Packet Radio Service) functionality for another entity.
-
C.
supportsGSM
Indicates that one entity provides compatibility with or operational support for GSM (Global System for Mobile communications) technology for another entity.
-
D.
supports2G
Indicates that one entity provides compatibility with or operational backing for 2G (second-generation) mobile network technology for another entity.
-
E.
supportsA-GPS
Indicates that one entity provides compatibility with or functionality for Assisted GPS (A-GPS) 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff77882c81909774aefc57ccca3e |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.