Triple
T16250678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Break My Stride |
E394495
|
entity |
| Predicate | yearEndChartUSBillboardHot1001984 |
P19929
|
FINISHED |
| Object | 40 |
—
|
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: 40 | Statement: [Break My Stride, yearEndChartUSBillboardHot1001984, 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearEndChartUSBillboardHot1001984 Context triple: [Break My Stride, yearEndChartUSBillboardHot1001984, 40]
-
A.
yearEndChartUSBillboardHot100
chosen
Indicates that the subject achieved a position on the U.S. Billboard Hot 100 year-end chart in the specified year.
-
B.
enteredBillboardHot100Top10Year
Indicates that an entity (typically a song or artist) reached the top 10 positions of the Billboard Hot 100 chart in a specified year.
-
C.
chartPeakDateUSBillboardHot100
Indicates the date on which a song or album reached its highest position on the US Billboard Hot 100 chart.
-
D.
chartPositionUSBillboardHot100Peak
Indicates the highest ranking an item has ever reached on the US Billboard Hot 100 chart.
-
E.
weeksAtNumberOneUSBillboardHot100
Indicates the number of weeks a song or recording remained at the #1 position on the US Billboard Hot 100 chart.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2459606f88190a53905186f7f73be |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.