Triple
T7089457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazon Fire Phone |
E165153
|
entity |
| Predicate | launchPrice |
P33098
|
FINISHED |
| Object | $199 on contract (32 GB model) |
—
|
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: $199 on contract (32 GB model) | Statement: [Amazon Fire Phone, launchPrice, $199 on contract (32 GB model)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchPrice Context triple: [Amazon Fire Phone, launchPrice, $199 on contract (32 GB model)]
-
A.
launchPriceDescription
Indicates the descriptive text explaining the initial price at which a product or service is first launched or offered.
-
B.
actualLaunchPrice
Indicates the price at which something was actually launched or first offered, as opposed to its planned or advertised launch price.
-
C.
launchPriceStandardEditionUSD
chosen
Indicates the original selling price, in U.S. dollars, of the standard edition of a product at the time it was first launched.
-
D.
launchPriceRegion
Indicates the geographic region or market in which a product’s initial launch price applies.
-
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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e52ec0348190ac090c2fee3edfb8 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.