Triple
T31880118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Shook Up |
E813858
|
entity |
| Predicate | chartPositionUSBestSellersInStores |
P180450
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [All Shook Up, chartPositionUSBestSellersInStores, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chartPositionUSBestSellersInStores Context triple: [All Shook Up, chartPositionUSBestSellersInStores, 1]
-
A.
reportedlyStores
Indicates that an entity is said or believed, based on reports or claims, to store or hold another entity, without confirming that this storage actually occurs.
-
B.
favoriteStore
Indicates that one entity is the preferred or most liked store of another entity.
-
C.
hasRetailPresenceIn
Indicates that an entity conducts retail operations or maintains a retail outlet, store, or sales presence within a specified location.
-
D.
hasStoreLocation
Indicates that an entity operates or maintains a store at a specified physical location.
-
E.
associatedRetailer
Indicates that one entity has a business or operational connection with a particular retailer, such as partnership, distribution, or sales affiliation.
- F. None of above. chosen
Provenance (4 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 30, 2026, 11:56 p.m.