Triple
T28958440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elastic Heart |
E731826
|
entity |
| Predicate | notableChartPerformance |
—
|
GENERATED |
| Object | top 20 in multiple countries |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableChartPerformance Context triple: [Elastic Heart, notableChartPerformance, top 20 in multiple countries]
-
A.
notableSingleChartPerformance
Indicates that an entity achieved a particularly significant or distinguished performance on a music singles chart.
-
B.
notableChartSuccessIn
Indicates that an entity has achieved significant or noteworthy success on music or performance charts within a specified region, market, or chart system.
-
C.
notableChartAchievement
chosen
Indicates that an entity has achieved a significant or distinguished position or milestone on a recognized ranking or performance chart.
-
D.
yearOfNotableChartSuccess
Indicates the specific year in which an entity achieved notable success on a music chart.
-
E.
hasNotableChartingStatus
Indicates that an entity has achieved a specific, noteworthy position or performance on an official chart or ranking.
- F. None of above.
Provenance (1 batch)
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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 8:49 a.m.