Triple
T29225838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Right Round |
E740931
|
entity |
| Predicate | digitalSalesRecord |
P4916
|
FINISHED |
| Object | broke US first-week digital sales record in 2009 |
—
|
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: broke US first-week digital sales record in 2009 | Statement: [Right Round, digitalSalesRecord, broke US first-week digital sales record in 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalSalesRecord Context triple: [Right Round, digitalSalesRecord, broke US first-week digital sales record in 2009]
-
A.
digitalSalesMilestone
chosen
Indicates that a specific target or significant achievement has been reached in the context of digital product or service sales.
-
B.
recordSale
Indicates that an entity documents or logs the completion of a sale transaction involving another entity.
-
C.
digitalProduct
Indicates that one entity is a product that exists in digital form or is delivered electronically rather than physically.
-
D.
recordAtSale
Indicates that something is documented or captured at the time a sale transaction occurs.
-
E.
soldProducts
Indicates that an entity has sold certain products to another entity or in a particular context.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66435c820819085ae81501d7b0775 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:16 p.m.