Triple

T2556919
Position Surface form Disambiguated ID Type / Status
Subject Stephen Elop E56748 entity
Predicate strategicPartnershipManaged P34923 FINISHED
Object Nokia–Microsoft smartphone partnership LITERAL 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–Microsoft smartphone partnership | Statement: [Stephen Elop, strategicPartnershipManaged, Nokia–Microsoft smartphone partnership]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: strategicPartnershipManaged
Context triple: [Stephen Elop, strategicPartnershipManaged, Nokia–Microsoft smartphone partnership]
  • A. managingPartner
    Indicates that one entity serves as the primary managing partner responsible for overseeing and directing the operations or affairs of another entity.
  • B. cooperationPartner chosen
    Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
  • C. councilPartner
    Indicates a formal collaborative relationship in which an entity serves as a partner within or to a council.
  • D. coManagedWith
    Indicates that two or more entities share joint responsibility or authority in managing the same resource, project, or process.
  • E. managedIn
    Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
  • F. None of above.

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_69ab4a4bfec081908039988ec4c86e28 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd5a33234819082ad49fa6594b6be completed March 7, 2026, 7:37 a.m.
PD Predicate disambiguation batch_69abd0c8b6f08190a68645db3e8b779a completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:48 p.m.