Triple

T35806633
Position Surface form Disambiguated ID Type / Status
Subject Chokeslam E1035117 entity
Predicate secondaryAction P199608 FINISHED
Object slamming the opponent onto the mat 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: slamming the opponent onto the mat | Statement: [Chokeslam, secondaryAction, slamming the opponent onto the mat]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: secondaryAction
Context triple: [Chokeslam, secondaryAction, slamming the opponent onto the mat]
  • A. secondaryFunction
    Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
  • B. secondaryTo
    Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
  • C. secondaryActivity
    Indicates that an entity engages in an additional, non-primary activity or role alongside its main activity.
  • D. secondAct
    Indicates that an entity performs, participates in, or is associated with the second act or phase within a larger, ordered sequence of actions or events.
  • E. secondaryTarget
    Indicates that an entity serves as an additional or subordinate target in relation to a primary target within a given context or action.
  • F. None of above. chosen

Provenance (4 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_69ff48199b1c8190bb05872f8a4f4673 completed May 9, 2026, 2:43 p.m.
PD Predicate disambiguation batch_69ff4746b1cc8190854f70a124df7d04 completed May 9, 2026, 2:40 p.m.
PDg Predicate description generation batch_69ff4818bb288190b4a27576fad18e23 completed May 9, 2026, 2:43 p.m.
Created at: May 3, 2026, 4:06 p.m.