Triple
T36028570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koei-Kan karate |
E1042196
|
entity |
| Predicate | usesStrikingTechniques |
P66641
|
FINISHED |
| Object | punches |
—
|
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: punches | Statement: [Koei-Kan karate, usesStrikingTechniques, punches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStrikingTechniques Context triple: [Koei-Kan karate, usesStrikingTechniques, punches]
-
A.
usesStrikes
chosen
Indicates that one entity employs or relies on strikes as a method, tactic, or means to achieve a goal or exert influence over another entity or situation.
-
B.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
C.
methodOfCombat
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
-
D.
hasDramaticTechnique
Indicates that one entity employs, features, or is characterized by a particular dramatic technique associated with another entity.
-
E.
skillUsedFor
Indicates that a particular skill is employed or applied to perform, achieve, or facilitate a specific task, goal, or function.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4:07 p.m.