Triple
T14476624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Footfalls |
E358988
|
entity |
| Predicate | hasMovementPattern |
P45058
|
FINISHED |
| Object | repetitive pacing on stage |
—
|
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: repetitive pacing on stage | Statement: [Footfalls, hasMovementPattern, repetitive pacing on stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMovementPattern Context triple: [Footfalls, hasMovementPattern, repetitive pacing on stage]
-
A.
hasMovementType
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
-
B.
hasMovementStructure
chosen
Indicates that one entity possesses or is characterized by a particular structure or pattern of movement.
-
C.
hasMovementVariant
Indicates that one movement is an alternative or variant form of another movement.
-
D.
hasSubmovement
Indicates that a movement or action is composed of, or contains within it, a smaller constituent movement.
-
E.
hasKeyMovement
Indicates that one entity possesses or defines the primary or characteristic movement pattern associated with another entity.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9248edb48190a74eb032aeaac027 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.