Triple
T5270108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo DS |
E119234
|
entity |
| Predicate | soldUnitsWorldwide |
P44135
|
FINISHED |
| Object | over 154 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 154 million units | Statement: [Nintendo DS, soldUnitsWorldwide, over 154 million units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soldUnitsWorldwide Context triple: [Nintendo DS, soldUnitsWorldwide, over 154 million units]
-
A.
salesWorldwide
Indicates a relationship where an entity’s sales figures or activities are measured, reported, or occur across multiple countries or global markets.
-
B.
soldCopies
chosen
Indicates that a certain number of copies of an item were sold by a seller (or in a context) to buyers.
-
C.
soldDuring
Indicates that a selling transaction or event occurred within the time span of a specified period or event.
-
D.
usedWorldwide
Indicates that something is utilized or applied across many countries or regions around the world.
-
E.
soldAs
Indicates that one entity is marketed, offered, or presented to others under the name, form, or role of another 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.