Triple

T16154247
Position Surface form Disambiguated ID Type / Status
Subject Nokia 8890 E391995 entity
Predicate relatedModel P37 FINISHED
Object Nokia 8860 E390056 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 8860 | Statement: [Nokia 8890, relatedModel, Nokia 8860]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nokia 8860
Context triple: [Nokia 8890, relatedModel, Nokia 8860]
  • A. Nokia 8860 chosen
    The Nokia 8860 is a late-1990s premium mobile phone known for its sleek sliding cover design and compact, stylish metal-clad body.
  • B. Nokia 8850
    The Nokia 8850 is a late-1990s premium mobile phone known for its compact size, sliding keypad cover, and stylish metallic design.
  • C. Nokia 6680
    The Nokia 6680 is a mid-2000s 3G smartphone known for its Symbian-based capabilities, dual cameras, and role in popularizing early mobile multimedia and video calling.
  • D. Nokia 8800
    The Nokia 8800 is a premium stainless-steel slider mobile phone known for its high-end materials, minimalist design, and status-symbol appeal in the mid-2000s.
  • E. Nokia 8910
    The Nokia 8910 is a premium early-2000s mobile phone known for its titanium sliding cover, high-end build quality, and status-symbol positioning in Nokia’s luxury lineup.
  • 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_69d87f1c65e48190aa2b4c472e9bafc4 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e21e57e95c8190ae4ed641be974ce5 completed April 17, 2026, 11:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69fff7ae46dc81908cba9152a6080c3a completed May 10, 2026, 3:12 a.m.
Created at: April 10, 2026, 5:01 a.m.