Triple
T11249431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hellblade: Senua's Sacrifice |
E266286
|
entity |
| Predicate | approximateSales |
P20940
|
FINISHED |
| Object | over 1 million copies |
—
|
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 1 million copies | Statement: [Hellblade: Senua's Sacrifice, approximateSales, over 1 million copies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateSales Context triple: [Hellblade: Senua's Sacrifice, approximateSales, over 1 million copies]
-
A.
salePriceApproximate
Indicates that the recorded sale price is an estimated or approximate value rather than an exact amount.
-
B.
approximateAudienceSize
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
C.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
D.
soldRecordsEstimate
chosen
Indicates an approximate number of sales transactions or records associated with an entity.
-
E.
areEstimatedIn
Indicates that a value or quantity is approximated or inferred within a specified context, framework, or unit.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e93212448190b46b3799b0bdfa0f |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.