Triple
T24203346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go to Sleep |
E600036
|
entity |
| Predicate | kayfabeEffect |
P119273
|
FINISHED |
| Object | knockout |
—
|
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: knockout | Statement: [Go to Sleep, kayfabeEffect, knockout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kayfabeEffect Context triple: [Go to Sleep, kayfabeEffect, knockout]
-
A.
kayfabe
Indicates the relationship or action of presenting events, rivalries, or personas as real and unscripted, despite being staged or predetermined.
-
B.
kayfabeStatus
Indicates the status of whether an event, action, or portrayal is being presented as part of the scripted, in-universe narrative (kayfabe) or acknowledged as non-scripted reality.
-
C.
gimmick
Indicates that an entity uses or features a novel, attention-grabbing trick or device primarily intended to attract interest rather than provide substantive value.
-
D.
wrestlesUnderMask
Indicates that one entity participates in wrestling while concealing their identity with a mask.
-
E.
defeatEffect
chosen
Indicates that one entity’s defeat causes a particular outcome or change to occur for another entity or the overall situation.
- 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_69f27ca38c148190ae65cd692567d43d |
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.