Triple
T23261532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Let 'Em Burn |
E582027
|
entity |
| Predicate | releaseAfter |
P126350
|
FINISHED |
| Object | disbandment of Hot Boys |
—
|
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: disbandment of Hot Boys | Statement: [Let 'Em Burn, releaseAfter, disbandment of Hot Boys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseAfter Context triple: [Let 'Em Burn, releaseAfter, disbandment of Hot Boys]
-
A.
releasedFollowing
chosen
Indicates that one entity was released after another entity, in a subsequent or later release order.
-
B.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
C.
releasedAfterSuccessOf
Indicates that one entity was released following, and likely in response to, the successful performance or reception of another entity.
-
D.
releasedInsteadOf
Indicates that one entity was released in place of, or as a substitute for, another entity that was not released.
-
E.
releasedFor
Indicates that something has been made available or authorized for public use, distribution, or access.
- 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_69f194c9f33c819082ef6b380fc594dd |
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.