Triple
T34768516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A New Day Yesterday |
E1002285
|
entity |
| Predicate | featuresCoverSong |
P133538
|
FINISHED |
| Object | Cradle Rock |
E2110802
|
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: Cradle Rock | Statement: [A New Day Yesterday, featuresCoverSong, Cradle Rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCoverSong Context triple: [A New Day Yesterday, featuresCoverSong, Cradle Rock]
-
A.
featuresSongwriterCovered
Indicates that one entity includes or highlights a songwriter whose work has been covered in a song or performance by another entity.
-
B.
featuresSongFrom
Indicates that one musical work includes or incorporates a song originating from another source.
-
C.
featuresSongAbout
Indicates that one entity includes or presents a song whose subject or content is about another entity.
-
D.
featuresSongwriter
Indicates that a musical work includes or credits a particular person as its songwriter.
-
E.
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.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a0361c6d76481909332b28ab01b0ef7 |
completed | May 12, 2026, 5:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376f9ec6c4819087580a90ffa15101 |
completed | June 21, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_6a0360b3818c819084bbecf705475f4f |
completed | May 12, 2026, 5:17 p.m. |
Created at: May 3, 2026, 3:59 p.m.