Triple
T35527202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gyaku ude-garami |
E1026703
|
entity |
| Predicate | controlPosition |
P198370
|
FINISHED |
| Object | side control |
—
|
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: side control | Statement: [gyaku ude-garami, controlPosition, side control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlPosition Context triple: [gyaku ude-garami, controlPosition, side control]
-
A.
controlDirection
Indicates that one entity exerts influence or guidance over the orientation, course, or movement direction of another entity.
-
B.
controlStand
Indicates that one entity manages, directs, or regulates the operation or behavior of another entity or system.
-
C.
controlsMovementBetween
Indicates a relationship where one entity regulates, directs, or manages the movement or transfer of another entity between locations or states.
-
D.
controlStatus
Indicates that one entity has a particular level, state, or condition of control over another entity or process.
-
E.
controlContext
Indicates that one entity governs, constrains, or determines the conditions under which another entity operates or is interpreted.
- 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_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69fedfd850ec81909b55f90dc850167e |
completed | May 9, 2026, 7:18 a.m. |
Created at: May 3, 2026, 4:04 p.m.