Triple
T5136997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Nintendo Entertainment System |
E115849
|
entity |
| Predicate | lifetimeSalesApproximate |
P20940
|
FINISHED |
| Object | 49 million units |
—
|
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: 49 million units | Statement: [Super Nintendo Entertainment System, lifetimeSalesApproximate, 49 million units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifetimeSalesApproximate Context triple: [Super Nintendo Entertainment System, lifetimeSalesApproximate, 49 million units]
-
A.
digitalSalesMilestone
Indicates that a specific target or significant achievement has been reached in the context of digital product or service sales.
-
B.
soldDuring
Indicates that a selling transaction or event occurred within the time span of a specified period or event.
-
C.
hasAlbumSales
Indicates that an entity (typically an album or artist) is associated with a specific quantity or record of album sales.
-
D.
soldCopies
Indicates that a certain number of copies of an item were sold by a seller (or in a context) to buyers.
-
E.
soldRecordsEstimate
chosen
Indicates an approximate number of sales transactions or records associated with an entity.
- 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_69bd44459a988190a772a5c2ec6a1965 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7fef2e8c8190982dd67f50295ada |
completed | March 20, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69bd77ac2fc48190abeebb003a82384c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:43 p.m.