Triple
T19994318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Album |
E494151
|
entity |
| Predicate | containsSongWithHitStatus |
P138261
|
FINISHED |
| Object | Radioactive |
—
|
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: Radioactive | Statement: [The Album, containsSongWithHitStatus, Radioactive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSongWithHitStatus Context triple: [The Album, containsSongWithHitStatus, Radioactive]
-
A.
hasSong
Indicates that one entity possesses, features, or includes a particular song.
-
B.
containsSongReferencing
Indicates that one entity (such as a work, collection, or playlist) includes at least one song that makes an explicit reference to another specified entity.
-
C.
includesSongsFrom
Indicates that one collection, playlist, or set contains one or more songs that originate from another specified source or group.
-
D.
sangSongsIn
Indicates that one entity performed or vocalized songs in the context, location, or event associated with another entity.
-
E.
hasHitSingleOnChart
Indicates that an entity (such as an artist or song) has achieved at least one single that appeared on a specified music chart.
- F. None of above. chosen
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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe306548190a6924ce3798a4d3d |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:31 p.m.