Triple
T16944583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 6210 |
E411035
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Nokia 6310 |
E418488
|
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 6310 | Statement: [Nokia 6210, successor, Nokia 6310]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nokia 6310 Context triple: [Nokia 6210, successor, Nokia 6310]
-
A.
Nokia 6310
chosen
The Nokia 6310 is a classic early-2000s GSM mobile phone renowned for its durability, long battery life, and popularity as a reliable business handset.
-
B.
Nokia 6100
The Nokia 6100 is a compact early-2000s GSM mobile phone known for its color display, lightweight candybar design, and popularity as a reliable mid-range handset.
-
C.
Nokia 6610
The Nokia 6610 is a classic early-2000s GSM mobile phone known for its durable candybar design, color display, and long battery life.
-
D.
Nokia 6210
The Nokia 6210 is a classic early-2000s GSM mobile phone known for its robust build, long battery life, and popularity among business users.
-
E.
Nokia 6300
The Nokia 6300 is a mid-2000s candybar-style mobile phone known for its slim stainless-steel design, reliability, and popularity as a classic feature phone.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb08da88190b07c32652bbc1534 |
completed | April 18, 2026, 6:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00cfeca4208190a3b9270869063d3d |
completed | May 10, 2026, 6:35 p.m. |
Created at: April 10, 2026, 5:31 a.m.