Triple

T28192123
Position Surface form Disambiguated ID Type / Status
Subject Poison Clan E716342 entity
Predicate notableWork P4 FINISHED
Object Nasty As They Wanna Be II
Nasty As They Wanna Be II is a hip hop album by Miami-based group Poison Clan, known for its explicit lyrics and Southern bass-influenced sound.
E1811928 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: Nasty As They Wanna Be II | Statement: [Poison Clan, notableWork, Nasty As They Wanna Be II]
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: Nasty As They Wanna Be II
Triple: [Poison Clan, notableWork, Nasty As They Wanna Be II]
Generated description
Nasty As They Wanna Be II is a hip hop album by Miami-based group Poison Clan, known for its explicit lyrics and Southern bass-influenced sound.

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_69efd6b612f48190a72012b520afbd10 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f642ce9aec8190bb3e76ca66824af7 completed May 2, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a16070567f08190800f300d9d441846 completed May 26, 2026, 8:48 p.m.
NEDg Description generation batch_6a16155ada008190b5d249824da6d04e completed May 26, 2026, 9:49 p.m.
NED2 Entity disambiguation (via description) batch_6a16160ccb488190a1dfc9c3ec8a0f4a completed May 26, 2026, 9:52 p.m.
Created at: April 27, 2026, 10:25 p.m.