Triple
T3126991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazing |
E65319
|
entity |
| Predicate | featuredVocalRole |
P8086
|
FINISHED |
| Object | guest verse by Young Jeezy |
—
|
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: guest verse by Young Jeezy | Statement: [Amazing, featuredVocalRole, guest verse by Young Jeezy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredVocalRole Context triple: [Amazing, featuredVocalRole, guest verse by Young Jeezy]
-
A.
featuresVocalist
chosen
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
-
B.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
C.
isVocalShowcaseFor
Indicates that something serves as a performance or context specifically designed to highlight and display another entity’s vocal abilities.
-
D.
primaryVocalist
Indicates that the subject is the main singer or lead vocal performer for the object (such as a song, track, or musical work).
-
E.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada544cb648190b5ed430dbd561d52 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.