Triple
T32451348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Not For Radio |
E829292
|
entity |
| Predicate | hasVocalInterludeBy |
P44280
|
FINISHED |
| Object | Puff Daddy |
—
|
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: Puff Daddy | Statement: [Not For Radio, hasVocalInterludeBy, Puff Daddy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVocalInterludeBy Context triple: [Not For Radio, hasVocalInterludeBy, Puff Daddy]
-
A.
containsInterludes
Indicates that one entity (typically a work or composition) includes one or more interludes within its structure.
-
B.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
C.
hasAdditionalVocalElements
Indicates that an entity includes extra vocal components or embellishments beyond its primary or standard vocal parts.
-
D.
hasVocalPerformanceBy
chosen
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
E.
isInterludeOnAlbum
Indicates that a track functions as an interlude within the context of a specific album.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 12:56 a.m.