Triple
T35527219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gyaku ude-garami |
E1026703
|
entity |
| Predicate | requiresGripOn |
P200826
|
FINISHED |
| Object | opponent’s wrist |
—
|
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: opponent’s wrist | Statement: [gyaku ude-garami, requiresGripOn, opponent’s wrist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresGripOn Context triple: [gyaku ude-garami, requiresGripOn, opponent’s wrist]
-
A.
hasGripType
Indicates that one entity possesses or uses a specific type or style of grip in relation to another entity or action.
-
B.
gripType
Indicates the manner or style in which one entity physically holds or grasps another.
-
C.
gripFeature
Indicates that one entity has a specific grip-related characteristic or functionality in relation to another entity.
-
D.
gripRule
Indicates a rule or constraint governing how something may be gripped, held, or grasped.
-
E.
cannotBeGraspedAs
Indicates that one entity is not capable of being mentally or conceptually understood in the manner or terms defined by another entity or perspective.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69ffb120b9988190b6361c69265033c0 |
completed | May 9, 2026, 10:11 p.m. |
Created at: May 3, 2026, 4:04 p.m.