Triple
T28958417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elastic Heart |
E731826
|
entity |
| Predicate | originalVersionFeature |
P127144
|
FINISHED |
| Object | The Weeknd |
—
|
NE NERFINISHED |
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: The Weeknd | Statement: [Elastic Heart, originalVersionFeature, The Weeknd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalVersionFeature Context triple: [Elastic Heart, originalVersionFeature, The Weeknd]
-
A.
originalFeature
Indicates that one entity is the initial or source feature from which another feature is derived, modified, or referenced.
-
B.
originalVersionRecordedBy
chosen
Indicates that the original version of a work (e.g., a song or recording) was recorded by a specific performer or recording entity.
-
C.
originalVersionStyle
Indicates that one entity represents the stylistic form or manner of expression used in the original version of another entity.
-
D.
originalRelease
Indicates the initial publication or first official release event of a work or product.
-
E.
originalTextVersion
Indicates that one text is the original version from which another text (such as a translation, revision, or adaptation) is derived.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: April 28, 2026, 8:49 a.m.