Triple
T27836718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "So Appalled" |
E703243
|
entity |
| Predicate | featuresVocalAdlibsBy |
P149125
|
FINISHED |
| Object | Swizz Beatz |
—
|
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: Swizz Beatz | Statement: ["So Appalled", featuresVocalAdlibsBy, Swizz Beatz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresVocalAdlibsBy Context triple: ["So Appalled", featuresVocalAdlibsBy, Swizz Beatz]
-
A.
featuresVocal
Indicates that one entity includes or presents the vocal performance or voice of another entity.
-
B.
featuresVocalInterjectionsBy
chosen
Indicates that something (such as a work or recording) contains vocal interjections performed or contributed by a specified entity.
-
C.
featuresVocalHarmonyBy
Indicates that the subject work includes vocal harmony performances contributed by the specified artist or group.
-
D.
featuresVocalPercussion
Indicates that the subject includes or makes use of vocal percussion (such as beatboxing or mouth-made rhythmic sounds) as part of its content or performance.
-
E.
featuresVocalist
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
- 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 27, 2026, 6 p.m.