Triple
T30651224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slow Drag |
E780263
|
entity |
| Predicate | footworkStyle |
P169981
|
FINISHED |
| Object | dragging the free foot along the floor |
—
|
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: dragging the free foot along the floor | Statement: [Slow Drag, footworkStyle, dragging the free foot along the floor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footworkStyle Context triple: [Slow Drag, footworkStyle, dragging the free foot along the floor]
-
A.
kickingStyle
Indicates the manner or technique with which an entity performs a kicking action in a given context.
-
B.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
C.
footType
Indicates the specific kind or classification of feet that an entity possesses or is characterized by.
-
D.
hasFootstomps
Indicates that one entity performs or possesses foot-stomping actions or behaviors in relation to another entity or context.
-
E.
danceAction
Indicates an action where an entity performs or engages in dancing, typically involving rhythmic or expressive body movements.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a98249081909b4be467f5a37110 |
completed | May 2, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:30 p.m.