Triple

T22767723
Position Surface form Disambiguated ID Type / Status
Subject Jeet Kune Do E563171 entity
Predicate strikingStrategy P31887 FINISHED
Object lead side forward for speed and power 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: lead side forward for speed and power | Statement: [Jeet Kune Do, strikingStrategy, lead side forward for speed and power]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: strikingStrategy
Context triple: [Jeet Kune Do, strikingStrategy, lead side forward for speed and power]
  • A. offensiveStrategy
    Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
  • B. strikeAction
    Indicates an action where one entity forcefully hits, attacks, or impacts another entity.
  • C. strikingAllowed
    Indicates that performing a physical strike (e.g., hitting or attacking) on the target entity is permitted under the given rules or conditions.
  • D. notableStrike
    Indicates that an entity is recognized for having carried out or been involved in a particularly significant or impactful strike (such as a labor strike, military strike, or similar major action).
  • E. strategyType chosen
    Indicates the specific kind or category of strategy associated with an entity or action.
  • 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_69e24552e11c81909c2d61578a558bd7 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17a81d3348190b005a43a5e03d406 completed April 29, 2026, 3:26 a.m.
PD Predicate disambiguation batch_69eed2b88d88819096015deb6a648801 completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:27 p.m.