Triple
T478206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia |
E9106
|
entity |
| Predicate | soldBusinessUnit |
P197
|
FINISHED |
| Object | Devices and Services business to Microsoft in 2014 |
—
|
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: Devices and Services business to Microsoft in 2014 | Statement: [Nokia, soldBusinessUnit, Devices and Services business to Microsoft in 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soldBusinessUnit Context triple: [Nokia, soldBusinessUnit, Devices and Services business to Microsoft in 2014]
-
A.
soldCompanyTo
chosen
Indicates that one entity transferred ownership of a company to another entity through a sale transaction.
-
B.
seller
Indicates a relationship where one entity offers or provides goods, services, or assets to another in exchange for payment or other compensation.
-
C.
hasSoldOver
Indicates that one entity has sold a quantity of something exceeding a specified threshold or the amount sold by another entity.
-
D.
attemptedSaleTo
Indicates that one entity tried, but did not necessarily succeed, to sell something to another entity.
-
E.
salesMilestone
Indicates that a specific sales target or threshold has been reached or surpassed.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f03f3fbc81909af6e4496d5e6c2a |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf017548190ae38ff3314a1ffa3 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.