Triple
T1936730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo GameCube |
E41458
|
entity |
| Predicate | retailPriceAtLaunch |
P4148
|
FINISHED |
| Object | 199.99 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: 199.99 USD | Statement: [Nintendo GameCube, retailPriceAtLaunch, 199.99 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retailPriceAtLaunch Context triple: [Nintendo GameCube, retailPriceAtLaunch, 199.99 USD]
-
A.
actualLaunchPrice
chosen
Indicates the price at which something was actually launched or first offered, as opposed to its planned or advertised launch price.
-
B.
launchPriceDescription
Indicates the descriptive text explaining the initial price at which a product or service is first launched or offered.
-
C.
launchPriceRegion
Indicates the geographic region or market in which a product’s initial launch price applies.
-
D.
salePriceApproximate
Indicates that the recorded sale price is an estimated or approximate value rather than an exact amount.
-
E.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2c5f6e481909b2d95861e2098f9 |
completed | March 7, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.