Triple
T19249298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vira |
E481346
|
entity |
| Predicate | stepCharacteristic |
P14493
|
FINISHED |
| Object | syncopated footwork |
—
|
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: syncopated footwork | Statement: [Vira, stepCharacteristic, syncopated footwork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stepCharacteristic Context triple: [Vira, stepCharacteristic, syncopated footwork]
-
A.
stepType
Indicates the specific kind or category of step an entity represents within a process or sequence.
-
B.
typicalStep
Indicates that an action, event, or sub-process is a standard or commonly occurring step within a larger process or procedure.
-
C.
transitionCharacteristic
Indicates a relationship where an entity is characterized by how it changes state or condition over time or between phases.
-
D.
stepReturns
Indicates that a particular step in a process or workflow yields, outputs, or hands back a specified result or value.
-
E.
movementCharacteristic
chosen
Indicates how an entity moves or behaves in motion, such as its style, pattern, or quality of movement.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb2f43e48190abab5257bec8e6aa |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.