Triple
T9237090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heat Wave (Linda Ronstadt song) |
E221964
|
entity |
| Predicate | chartSuccessPeriod |
P4919
|
FINISHED |
| Object | mid-1970s |
—
|
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: mid-1970s | Statement: [Heat Wave (Linda Ronstadt song), chartSuccessPeriod, mid-1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chartSuccessPeriod Context triple: [Heat Wave (Linda Ronstadt song), chartSuccessPeriod, mid-1970s]
-
A.
chartSuccessWith
Indicates a relationship where one entity measures, tracks, or visualizes the success or performance of another entity using charts or similar representations.
-
B.
chartPerformance
chosen
Indicates how well something ranks or behaves on a chart or leaderboard over a given period.
-
C.
chartSuccessInCountry
Indicates that something has achieved a measurable level of success on music or sales charts within a specified country.
-
D.
chartStatus
Indicates the current state or condition of a chart, such as whether it is active, updated, or in a particular workflow stage.
-
E.
chartingSingle
Indicates that an entity appears on a music chart as a single track release.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccf09e553081909cf864635cfc5dcc |
completed | April 1, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:29 p.m.