Triple

T37706971
Position Surface form Disambiguated ID Type / Status
Subject Nokia World 2010 E939221 entity
Predicate hasKeynoteSpeaker P9374 FINISHED
Object Anssi Vanjoki
Anssi Vanjoki is a Finnish business executive best known for his long career at Nokia, where he held several senior leadership roles in the mobile phone division.
E2248712 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: Anssi Vanjoki | Statement: [Nokia World 2010, hasKeynoteSpeaker, Anssi Vanjoki]
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: Anssi Vanjoki
Triple: [Nokia World 2010, hasKeynoteSpeaker, Anssi Vanjoki]
Generated description
Anssi Vanjoki is a Finnish business executive best known for his long career at Nokia, where he held several senior leadership roles in the mobile phone division.

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_69f76edb49dc8190b951dce9ce6ef789 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbae471674819082127a5b5e314805 completed May 6, 2026, 9:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a410cadf5ac8190a301f5e0c4724f67 completed June 28, 2026, 11:59 a.m.
NEDg Description generation batch_6a410d36ac008190b23036ecdf4159d5 completed June 28, 2026, 12:01 p.m.
NED2 Entity disambiguation (via description) batch_6a410e50a2d0819092ce4ff0863ecbc2 completed June 28, 2026, 12:06 p.m.
Created at: May 3, 2026, 4:18 p.m.