Triple
T25156645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Change We Must |
E626330
|
entity |
| Predicate | featuresReworkedSong |
P133538
|
FINISHED |
| Object | Hearts |
E795204
|
NE 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: Hearts | Statement: [Change We Must, featuresReworkedSong, Hearts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresReworkedSong Context triple: [Change We Must, featuresReworkedSong, Hearts]
-
A.
featuresReRecordedSong
chosen
Indicates that an entity (such as an album, release, or performance) includes a song that has been recorded again in a new version distinct from its original recording.
-
B.
featuresSongwriter
Indicates that a musical work includes or credits a particular person as its songwriter.
-
C.
featuresNewSong
Indicates that an entity presents, includes, or showcases a newly released song.
-
D.
featuresSongwriterCovered
Indicates that one entity includes or highlights a songwriter whose work has been covered in a song or performance by another entity.
-
E.
notableSongCharacteristic
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
- F. None of above.
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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1075c3f8a0819098ebcbb569e36d90 |
completed | May 22, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 18, 2026, 6:30 a.m.