Triple
T30651380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boogie |
E780267
|
entity |
| Predicate | featuresPosthumousPerformanceBy |
P102630
|
FINISHED |
| Object | Pop Smoke |
—
|
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: Pop Smoke | Statement: [Boogie, featuresPosthumousPerformanceBy, Pop Smoke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPosthumousPerformanceBy Context triple: [Boogie, featuresPosthumousPerformanceBy, Pop Smoke]
-
A.
includesPosthumousPerformanceBy
chosen
Indicates that something (such as a work, recording, or release) contains or features a performance by an entity that was released or presented after that entity’s death.
-
B.
featuredSongPerformancesFrom
Indicates that certain song performances are highlighted or prominently presented as originating from a particular source, event, or context.
-
C.
featuresSoloPerformancesBy
Indicates that the subject includes or showcases solo performances carried out by the specified performer or performers.
-
D.
recordedPerformanceOf
Indicates that one entity is a recorded version or capture of another entity’s performance.
-
E.
presentsPerformancesBy
Indicates that one entity organizes or stages performances that feature or are carried out by another entity.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0017dd31d08190aa5e9f72df83733a |
completed | May 10, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_6a0015a1deb88190b9cdaa60455b0a33 |
completed | May 10, 2026, 5:20 a.m. |
Created at: April 29, 2026, 8:30 p.m.