Triple
T24202909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jey Uso |
E600025
|
entity |
| Predicate | hasEntranceCatchphrase |
P63461
|
FINISHED |
| Object | Yeet |
—
|
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: Yeet | Statement: [Jey Uso, hasEntranceCatchphrase, Yeet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEntranceCatchphrase Context triple: [Jey Uso, hasEntranceCatchphrase, Yeet]
-
A.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
B.
hasEntranceGimmick
Indicates that an entity features a distinctive or notable gimmick, stunt, or special element associated with its entrance or initial appearance.
-
C.
hasCatchphraseStatus
Indicates whether an entity’s phrase or expression holds the status of being recognized as a catchphrase.
-
D.
hasCatchphraseStyle
Indicates that an entity’s catchphrase conforms to, or is characterized by, a particular stylistic pattern or manner of expression.
-
E.
openingCatchphrase
chosen
Indicates that one entity is a characteristic phrase or line regularly used by another entity at the beginning of a recurring performance, appearance, or communication.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca2d6708190ba20d00870d0af49 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:37 p.m.