Triple
T13718784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buy U a Drank (Shawty Snappin') |
E328970
|
entity |
| Predicate | containsSlangTerm |
P103428
|
FINISHED |
| Object | shawty |
—
|
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: shawty | Statement: [Buy U a Drank (Shawty Snappin'), containsSlangTerm, shawty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSlangTerm Context triple: [Buy U a Drank (Shawty Snappin'), containsSlangTerm, shawty]
-
A.
hasMeaningInEnglishSlang
chosen
Indicates that something (such as a word, phrase, or expression) carries a particular meaning specifically within English slang usage.
-
B.
containsProfanity
Indicates that the referenced content includes one or more profane, vulgar, or offensive expressions.
-
C.
isColloquialTerm
Indicates that one term is an informal or non-standard, colloquial way of referring to another term or concept.
-
D.
hasRhymingSlangExample
Indicates that one entity serves as an example of rhyming slang associated with another entity.
-
E.
hasColloquialVariety
Indicates that one linguistic form, expression, or variety is an informal, colloquial counterpart or version of another.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd439a121c81908cae964e7756274c |
completed | April 13, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.