Triple

T12889149
Position Surface form Disambiguated ID Type / Status
Subject Nokia E61 E308310 entity
Predicate hasVariant P455 FINISHED
Object Nokia E61i E308310 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 E61i | Statement: [Nokia E61, hasVariant, Nokia E61i]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Nokia E61i
Context triple: [Nokia E61, hasVariant, Nokia E61i]
  • A. Nokia E61 chosen
    The Nokia E61 is a business-oriented smartphone from Nokia’s Eseries line, featuring a full QWERTY keyboard and advanced email and connectivity capabilities for its time.
  • B. Nokia E6
    The Nokia E6 is a business-oriented smartphone featuring a QWERTY keyboard and touchscreen, running Symbian and known for its productivity and email capabilities.
  • C. Nokia E60
    The Nokia E60 is a business-oriented smartphone from Nokia's Eseries line, featuring advanced connectivity and productivity features for professional users.
  • D. Nokia E62
    The Nokia E62 is a business-oriented smartphone from Nokia's Eseries line, featuring a full QWERTY keyboard and designed primarily for email and productivity.
  • E. Nokia E63
    The Nokia E63 is a mid-range Symbian-based QWERTY smartphone designed for business and messaging, known for its solid build, email capabilities, and affordability in the late 2000s.
  • 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_69d7bdf7c1f0819098102569a8d8cbf5 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9714581988190afc720ffd7797860 completed April 10, 2026, 9:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6a5598ad08190bad57ccfb4e4e2b6 completed May 3, 2026, 1:31 a.m.
Created at: April 9, 2026, 5:39 p.m.