Triple
T15336589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N97 |
E366681
|
entity |
| Predicate | codename |
P2980
|
FINISHED |
| Object |
Nokia RX-51
Nokia RX-51 is the internal codename used by Nokia for the N97 smartphone during its development.
|
E1150864
|
NE FINISHED |
How this triple was built (4 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 RX-51 | Statement: [Nokia N97, codename, Nokia RX-51]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nokia RX-51 Context triple: [Nokia N97, codename, Nokia RX-51]
-
A.
Nokia 8150
The Nokia 8150 is a late-1990s GSM mobile phone known for its slim, stylish design and classic candybar form factor.
-
B.
Nokia 1600
The Nokia 1600 is a basic, durable candybar-style mobile phone introduced in the mid-2000s, known for its long battery life and reliability in emerging markets.
-
C.
Nokia 7710
The Nokia 7710 is a pioneering early smartphone notable for its large touchscreen, multimedia capabilities, and use of the Series 90 interface on the Symbian operating system.
-
D.
Nokia 6510
The Nokia 6510 is a compact early-2000s GSM mobile phone known for its durable design, integrated FM radio, and business-oriented features.
-
E.
Nokia 6021
The Nokia 6021 is a mid-2000s business-oriented mobile phone known for its durable design, Bluetooth connectivity, and focus on reliability over multimedia features.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Nokia RX-51 Triple: [Nokia N97, codename, Nokia RX-51]
Generated description
Nokia RX-51 is the internal codename used by Nokia for the N97 smartphone during its development.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Nokia RX-51 Target entity description: Nokia RX-51 is the internal codename used by Nokia for the N97 smartphone during its development.
-
A.
Nokia 8150
The Nokia 8150 is a late-1990s GSM mobile phone known for its slim, stylish design and classic candybar form factor.
-
B.
Nokia 1600
The Nokia 1600 is a basic, durable candybar-style mobile phone introduced in the mid-2000s, known for its long battery life and reliability in emerging markets.
-
C.
Nokia 7710
The Nokia 7710 is a pioneering early smartphone notable for its large touchscreen, multimedia capabilities, and use of the Series 90 interface on the Symbian operating system.
-
D.
Nokia 6510
The Nokia 6510 is a compact early-2000s GSM mobile phone known for its durable design, integrated FM radio, and business-oriented features.
-
E.
Nokia 6021
The Nokia 6021 is a mid-2000s business-oriented mobile phone known for its durable design, Bluetooth connectivity, and focus on reliability over multimedia features.
- F. None of above. chosen
Provenance (5 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e11b22c81908280efe65acd5454 |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff01f11b88819089342e8b088bc95e |
completed | May 9, 2026, 9:44 a.m. |
| NEDg | Description generation | batch_69ff02de46948190ac9b9f87313a8442 |
completed | May 9, 2026, 9:48 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ff0341238c8190a7d0473ad9ab702c |
completed | May 9, 2026, 9:49 a.m. |
Created at: April 10, 2026, 3:17 a.m.