Triple
T26367963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dream Shake post move |
E660393
|
entity |
| Predicate | counterMoveTo |
P100355
|
FINISHED |
| Object | physical post defense |
—
|
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: physical post defense | Statement: [Dream Shake post move, counterMoveTo, physical post defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: counterMoveTo Context triple: [Dream Shake post move, counterMoveTo, physical post defense]
-
A.
commonMove
Indicates that two or more entities share the same movement or relocation event, occurring together or in an identical manner.
-
B.
counterattackBy
Indicates that an entity launches a retaliatory attack in response to an initial attack carried out by another entity.
-
C.
moves
Indicates that an entity changes its position or location over time, typically from one place to another.
-
D.
movesFrom
Indicates that an entity changes location by departing or originating from a specified place.
-
E.
counterplay
chosen
Indicates a responsive action or strategy taken to oppose, mitigate, or neutralize another party’s move or advantage.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 26, 2026, 10:56 p.m.