Triple
T18482878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24 Hrs. to Live |
E451605
|
entity |
| Predicate | hasMultipleVersesByDifferentRappers |
P131829
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [24 Hrs. to Live, hasMultipleVersesByDifferentRappers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleVersesByDifferentRappers Context triple: [24 Hrs. to Live, hasMultipleVersesByDifferentRappers, yes]
-
A.
hasMultipleVerses
Indicates that something, typically a song, poem, or text, consists of more than one verse.
-
B.
hasLyricalVariant
Indicates that one item has an alternative version that differs in its lyrics while remaining related to the original.
-
C.
hasCoverVersions
Indicates that a musical work has one or more recorded versions performed or produced by artists other than the original creator.
-
D.
hasPoemOrRhymeVersion
Indicates that one entity is a poem or rhyme version, adaptation, or variant of another entity.
-
E.
hasGuestVerseBy
Indicates that a work (such as a song or track) includes a guest verse performed by a specified artist.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d49a1881908cc2ad6132953c96 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:35 a.m.