Triple
T12718087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 3350 |
E303899
|
entity |
| Predicate | relatedModel |
P37
|
FINISHED |
| Object | Nokia 3310 |
E286147
|
NE 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: Nokia 3310 | Statement: [Nokia 3350, relatedModel, Nokia 3310]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nokia 3310 Context triple: [Nokia 3350, relatedModel, Nokia 3310]
-
A.
Nokia 3300
The Nokia 3300 is a music-focused mobile phone from the early 2000s featuring a distinctive gamepad-style keypad layout and integrated MP3 player.
-
B.
Nokia 3510
The Nokia 3510 is an early 2000s GSM mobile phone known for introducing polyphonic ringtones to Nokia’s mass-market lineup and offering a durable, colorful design.
-
C.
Nokia 3410
The Nokia 3410 is an early-2000s GSM mobile phone known for its durable design, long battery life, and support for Java-based games and applications.
-
D.
Nokia 3310 (2017)
chosen
The Nokia 3310 (2017) is a modern reimagining of Nokia’s classic feature phone, known for its nostalgic design, long battery life, and simple, durable build.
-
E.
Nokia 3110 classic
The Nokia 3110 classic is a mid-2000s candybar mobile phone known for its durable design, long battery life, and straightforward calling and texting features.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9625d9da48190ab377f9328a0e1f5 |
completed | April 10, 2026, 8:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d5ea02e08190b3be1fdfe86b4ee5 |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 5:23 p.m.