Triple

T4762671
Position Surface form Disambiguated ID Type / Status
Subject Kabaddi E105732 entity
Predicate defensiveObjective P56145 FINISHED
Object stop raider and prevent return to midline 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: stop raider and prevent return to midline | Statement: [Kabaddi, defensiveObjective, stop raider and prevent return to midline]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defensiveObjective
Context triple: [Kabaddi, defensiveObjective, stop raider and prevent return to midline]
  • A. objectiveOfDefenders chosen
    Indicates that a particular goal, task, or purpose is assigned to or pursued by the defenders in a given context.
  • B. defensiveOperation
    Indicates actions or measures undertaken to protect, guard, or defend a target against threats or attacks.
  • C. protectionObjective
    Indicates that one entity has the goal or purpose of safeguarding, defending, or preserving another entity or its interests.
  • D. opponentObjective
    Indicates that one entity is the target or goal that an opposing entity aims to counter, defeat, or prevent from succeeding.
  • E. defensiveStructure
    Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
  • 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_69bd43f14cac819081c7c69803648211 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd686ef1b08190ad60375592c9d6c0 completed March 20, 2026, 3:31 p.m.
PD Predicate disambiguation batch_69bd622807f881908e4bcb14f7731bac completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:20 p.m.