Triple
T23547082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swizz Beatz Presents G.H.E.T.T.O. Stories |
E577927
|
entity |
| Predicate | featuresVariousArtists |
P152749
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Swizz Beatz Presents G.H.E.T.T.O. Stories, featuresVariousArtists, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresVariousArtists Context triple: [Swizz Beatz Presents G.H.E.T.T.O. Stories, featuresVariousArtists, true]
-
A.
featuresArtistAs
Indicates that one entity includes or presents another entity in the role of an artist (e.g., a work, event, or product featuring a specific artist).
-
B.
featuresIndieMusicScene
Indicates that something includes, highlights, or is characterized by an independent (indie) music scene.
-
C.
featuresMusician
Indicates that something (such as a work, event, or recording) prominently includes or showcases a particular musician.
-
D.
featuresDJ
Indicates that an entity includes or presents a DJ as part of its offering or composition.
-
E.
featuresSongwriter
Indicates that a musical work includes or credits a particular person as its songwriter.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aecb567c8190a54d2c3b63282af5 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:11 p.m.