Triple
T20166119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Game Gear |
E491827
|
entity |
| Predicate | unitsSoldWorldwideApprox |
P44135
|
FINISHED |
| Object | 10.6 million |
—
|
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: 10.6 million | Statement: [Sega Game Gear, unitsSoldWorldwideApprox, 10.6 million]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitsSoldWorldwideApprox Context triple: [Sega Game Gear, unitsSoldWorldwideApprox, 10.6 million]
-
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.
playedWorldwide
Indicates that something (such as a performance, event, or media content) has been presented or made available in multiple countries across the world.
-
D.
usedWorldwide
Indicates that something is utilized or applied across many countries or regions around the world.
-
E.
soldUntil
Indicates that the availability or sale of an item continues up to, but not beyond, a specified time or date.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668442d2c81908bb1a0fac9895b5e |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.