Triple
T17676753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Stadia |
E440658
|
entity |
| Predicate | StadiaProPriceAtLaunch |
P4148
|
FINISHED |
| Object | 9.99 USD per month |
—
|
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: 9.99 USD per month | Statement: [Google Stadia, StadiaProPriceAtLaunch, 9.99 USD per month]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: StadiaProPriceAtLaunch Context triple: [Google Stadia, StadiaProPriceAtLaunch, 9.99 USD per month]
-
A.
launchPriceStandardEditionUSD
Indicates the original selling price, in U.S. dollars, of the standard edition of a product at the time it was first launched.
-
B.
actualLaunchPrice
chosen
Indicates the price at which something was actually launched or first offered, as opposed to its planned or advertised launch price.
-
C.
launchPriceDescription
Indicates the descriptive text explaining the initial price at which a product or service is first launched or offered.
-
D.
launchPriceRegion
Indicates the geographic region or market in which a product’s initial launch price applies.
-
E.
kitPriceAtIntroduction
Indicates the price assigned to a kit at the time it was first introduced or made available.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6d9ab88190ab0e25eac8b0101c |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:01 a.m.