Triple
T28191748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Who Want Smoke?? |
E716334
|
entity |
| Predicate | notableRemixFeaturing |
P75509
|
FINISHED |
| Object | G Herbo |
—
|
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: G Herbo | Statement: [Who Want Smoke??, notableRemixFeaturing, G Herbo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRemixFeaturing Context triple: [Who Want Smoke??, notableRemixFeaturing, G Herbo]
-
A.
notableRemixBy
Indicates that one creative work has a particularly recognized or significant remix created by a specified artist or entity.
-
B.
hasRemixFeaturing
chosen
Indicates that an original work has a remix version that features an additional artist or artists not present in the original.
-
C.
notableTrack
Indicates that a particular track (such as a song or recording) is especially significant, well-known, or prominent in relation to the subject.
-
D.
notableChorus
Indicates that an entity is recognized for having a particularly prominent or distinguished chorus section.
-
E.
notableCollaboration
Indicates a significant joint effort or partnership between entities that produced a noteworthy shared outcome or work.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a009d623f6c8190b702e2892c52fbb2 |
completed | May 10, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_6a009a3050d48190b64567f28e6ea463 |
completed | May 10, 2026, 2:46 p.m. |
Created at: April 27, 2026, 10:25 p.m.