Triple
T16677697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nickelback |
E405254
|
entity |
| Predicate | hasGlobalSalesOver |
P10648
|
FINISHED |
| Object | 50 million records |
—
|
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: 50 million records | Statement: [Nickelback, hasGlobalSalesOver, 50 million records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlobalSalesOver Context triple: [Nickelback, hasGlobalSalesOver, 50 million records]
-
A.
hasSoldOver
chosen
Indicates that one entity has sold a quantity of something exceeding a specified threshold or the amount sold by another entity.
-
B.
hasGlobalMarketShare
Indicates that an entity possesses a specified proportion of sales or presence in the worldwide market relative to all competitors.
-
C.
hasGlobalReach
Indicates that an entity’s influence, operations, or impact extends across multiple countries or worldwide.
-
D.
hasAlbumSales
Indicates that an entity (typically an album or artist) is associated with a specific quantity or record of album sales.
-
E.
hasGlobalDistribution
Indicates that the related entity occurs, operates, or is present across most or all regions of the world rather than being confined to a specific locality or region.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37d6c805c81909fbe4fcb20eedbe1 |
completed | April 18, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.