Triple
T26232009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tommy Genesis |
E656056
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object |
100 Bad
"100 Bad" is a provocative, genre-blending hip-hop track by Canadian rapper Tommy Genesis that showcases her sexually explicit, confrontational lyrical style.
|
E1714249
|
NE 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: 100 Bad | Statement: [Tommy Genesis, notableWork, 100 Bad]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 100 Bad Triple: [Tommy Genesis, notableWork, 100 Bad]
Generated description
"100 Bad" is a provocative, genre-blending hip-hop track by Canadian rapper Tommy Genesis that showcases her sexually explicit, confrontational lyrical style.
Provenance (5 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d87924c8190904dda60a4bdead9 |
completed | May 2, 2026, 2:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a11859a1d148190adee8ee0275bcc56 |
completed | May 23, 2026, 10:46 a.m. |
| NEDg | Description generation | batch_6a11862050608190bf26431a0fb90b07 |
completed | May 23, 2026, 10:49 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a1186bd48e48190a397267a101ef076 |
completed | May 23, 2026, 10:51 a.m. |
Created at: April 26, 2026, 9 p.m.