Triple
T452428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skype |
E7156
|
entity |
| Predicate | acquisitionCostByMicrosoft |
P5105
|
FINISHED |
| Object | 8500000000 USD |
—
|
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: 8500000000 USD | Statement: [Skype, acquisitionCostByMicrosoft, 8500000000 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionCostByMicrosoft Context triple: [Skype, acquisitionCostByMicrosoft, 8500000000 USD]
-
A.
acquisitionCost
chosen
Indicates the monetary amount or value required to obtain or purchase an entity.
-
B.
acquisitionPrice
Indicates the monetary amount paid to acquire an asset, company, or item in a transaction.
-
C.
actualLaunchPrice
Indicates the price at which something was actually launched or first offered, as opposed to its planned or advertised launch price.
-
D.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
E.
purchasePrice
Indicates the monetary amount paid or agreed to be paid to acquire something in a purchase transaction.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef854f7481909dc2207faf0327ec |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede3187c8190a7ced078f0ec3476 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.