Triple
T35810183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phenomenal Forearm |
E1035207
|
entity |
| Predicate | moveSubtype |
P184145
|
FINISHED |
| Object | forearm smash |
—
|
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: forearm smash | Statement: [Phenomenal Forearm, moveSubtype, forearm smash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moveSubtype Context triple: [Phenomenal Forearm, moveSubtype, forearm smash]
-
A.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
B.
movedSeeTo
Indicates that one entity changed the location or position of another entity so that it could be seen from a new vantage point.
-
C.
moveCategory
Indicates a change in an entity’s classification from one category to another within a defined system or hierarchy.
-
D.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
E.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.