Triple
T29991143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackhammer |
E761881
|
entity |
| Predicate | componentMove |
P181667
|
FINISHED |
| Object | vertical suplex |
—
|
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: vertical suplex | Statement: [Jackhammer, componentMove, vertical suplex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentMove Context triple: [Jackhammer, componentMove, vertical suplex]
-
A.
clubMove
Indicates a change in a person's club affiliation, capturing the action of moving from one club to another.
-
B.
componentExchange
Indicates a relationship where one component provides, transfers, or receives data, energy, or other resources to or from another component.
-
C.
replacesComponentOf
Indicates that one entity takes the place of a specific component within another entity, substituting for that component in its role or function.
-
D.
compositionChanged
Indicates that the makeup or constituent elements of something have been altered from a previous state.
-
E.
contactMove
Indicates that one entity moves into or maintains physical contact with another entity.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: April 29, 2026, 6:38 p.m.