Triple
T488498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan Snyder |
E9932
|
entity |
| Predicate | salePrice |
P5867
|
FINISHED |
| Object | 6000000000 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: 6000000000 USD | Statement: [Dan Snyder, salePrice, 6000000000 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: salePrice Context triple: [Dan Snyder, salePrice, 6000000000 USD]
-
A.
purchasePrice
Indicates the monetary amount paid or agreed to be paid to acquire something in a purchase transaction.
-
B.
actualLaunchPrice
Indicates the price at which something was actually launched or first offered, as opposed to its planned or advertised launch price.
-
C.
relativePrice
Indicates a comparison of the cost or monetary value of one entity relative to another.
-
D.
acquisitionPrice
chosen
Indicates the monetary amount paid to acquire an asset, company, or item in a transaction.
-
E.
pricingStrategy
Indicates the approach or method used to set, adjust, or structure prices for products or services in a given context.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0df764481909811d9483dfbc4aa |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf63fbc819090ea6ca11f39116a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.