Triple
T14576749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N73 |
E342071
|
entity |
| Predicate | gprs |
P105879
|
FINISHED |
| Object | Class 11 |
—
|
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: Class 11 | Statement: [Nokia N73, gprs, Class 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gprs Context triple: [Nokia N73, gprs, Class 11]
-
A.
supportsGPRS
chosen
Indicates that one entity provides or is compatible with GPRS (General Packet Radio Service) functionality for another entity.
-
B.
supportsGSM
Indicates that one entity provides compatibility with or operational support for GSM (Global System for Mobile communications) technology for another entity.
-
C.
supports3G
Indicates that one entity provides or is compatible with 3G mobile network connectivity for another entity or for its operation.
-
D.
radioInterface
Indicates a relationship where one entity provides or defines the radio communication interface used by another entity for wireless connectivity or control.
-
E.
connectivity
Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f5ec448190b2ef887fdf7b633e |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.