Triple
T20433641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lil Jon |
E501194
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | Yeah! |
—
|
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: Yeah! | Statement: [Lil Jon, notableWork, Yeah!]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yeah! Context triple: [Lil Jon, notableWork, Yeah!]
-
A.
Yeah!
"Yeah!" is a notable work created by Sean Garrett, recognized as a significant contribution to his body of work.
-
B.
Yeah!
chosen
"Yeah!" is a 2004 hit R&B/hip-hop single by Usher featuring Lil Jon and Ludacris that became one of his signature songs and a global club anthem.
-
C.
Yes!
"Yes!" is a 2009 studio album by Canadian rapper and musician K-Os that blends hip hop with rock, reggae, and alternative influences.
-
D.
Yes!
"Yes!" is a 2014 acoustic-driven studio album by singer-songwriter Jason Mraz, noted for its mellow, folk-pop sound and themes of positivity and love.
-
E.
Yah
Yah is a shortened form of the Hebrew divine name often used in religious texts and songs to refer to the God of Israel.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685ecf7ac81908e9c2ef4348fb281 |
completed | April 20, 2026, 8 p.m. |
Created at: April 16, 2026, 11:31 a.m.