Triple
T5079745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo Entertainment System |
E114484
|
entity |
| Predicate | lifetimeSales |
P12595
|
FINISHED |
| Object | over 60 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: over 60 million units | Statement: [Nintendo Entertainment System, lifetimeSales, over 60 million units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifetimeSales Context triple: [Nintendo Entertainment System, lifetimeSales, over 60 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.
salesMilestone
chosen
Indicates that a specific sales target or threshold has been reached or surpassed.
-
C.
soldDuring
Indicates that a selling transaction or event occurred within the time span of a specified period or event.
-
D.
hasAlbumSales
Indicates that an entity (typically an album or artist) is associated with a specific quantity or record of album sales.
-
E.
soldCopies
Indicates that a certain number of copies of an item were sold by a seller (or in a context) to buyers.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74f86c988190aa026073ed435a45 |
completed | March 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69bd7159adc881909effd4382c395c66 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.