Triple
T23260947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poppin Them Bottles |
E582004
|
entity |
| Predicate | hasHostDJ |
P93557
|
FINISHED |
| Object | DJ Drama on Dedication 2 |
—
|
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: DJ Drama on Dedication 2 | Statement: [Poppin Them Bottles, hasHostDJ, DJ Drama on Dedication 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostDJ Context triple: [Poppin Them Bottles, hasHostDJ, DJ Drama on Dedication 2]
-
A.
hasMainDJOrProducer
chosen
Indicates that an entity (such as a music show, event, or recording) has a specific person or group serving as its primary DJ or producer.
-
B.
hasHostNation
Indicates that one entity serves as the host nation for another entity, such as an event, organization, or activity.
-
C.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
D.
hasOpeningHost
Indicates that an event, show, or program is hosted or introduced by a particular opening host.
-
E.
hostedDuring
Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
- 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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f194c9189c8190a13c17c635227f42 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:11 p.m.