Triple
T35808827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punt Kick |
E1035173
|
entity |
| Predicate | storylineEffect |
P126720
|
FINISHED |
| Object | kayfabe injury angle |
—
|
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: kayfabe injury angle | Statement: [Punt Kick, storylineEffect, kayfabe injury angle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storylineEffect Context triple: [Punt Kick, storylineEffect, kayfabe injury angle]
-
A.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
B.
narrativeEffect
chosen
Indicates how one event, action, or element in a story influences the progression, tone, or interpretation of the overall narrative.
-
C.
storylineEvent
Indicates that one event occurs as a distinct step or component within a larger narrative or storyline.
-
D.
storylineTone
Indicates the overall emotional quality or mood conveyed by the storyline in relation to an entity.
-
E.
storylineReason
Indicates that one event, action, or situation occurs as a narrative cause or justification for another within a storyline.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:06 p.m.