Triple
T671424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Pan Award |
E12978
|
entity |
| Predicate | salesThreshold |
P12595
|
FINISHED |
| Object | 1000000 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: 1000000 copies | Statement: [Golden Pan Award, salesThreshold, 1000000 copies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: salesThreshold Context triple: [Golden Pan Award, salesThreshold, 1000000 copies]
-
A.
salesMilestone
chosen
Indicates that a specific sales target or threshold has been reached or surpassed.
-
B.
digitalSalesMilestone
Indicates that a specific target or significant achievement has been reached in the context of digital product or service sales.
-
C.
thresholdFor
Indicates that one entity specifies the minimum or limiting value at which a condition, effect, or state involving another entity begins to occur or change.
-
D.
earlySalesMilestone
Indicates that a sales-related target or threshold was reached earlier than a planned or standard milestone time.
-
E.
hasSoldOver
Indicates that one entity has sold a quantity of something exceeding a specified threshold or the amount sold by 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a1b3682c8190a9b9a454480c3446 |
completed | March 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69a49d1a16c48190af89e3b078a4957e |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.