Triple
T1333455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zapin dance |
E28693
|
entity |
| Predicate | movementFeature |
P14493
|
FINISHED |
| Object | intricate foot patterns |
—
|
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: intricate foot patterns | Statement: [Zapin dance, movementFeature, intricate foot patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementFeature Context triple: [Zapin dance, movementFeature, intricate foot patterns]
-
A.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
B.
movementCharacteristic
chosen
Indicates how an entity moves or behaves in motion, such as its style, pattern, or quality of movement.
-
C.
movementRole
Indicates the specific function or capacity an entity has within a movement or motion-related activity (e.g., mover, path, source, or goal).
-
D.
movementDirection
Indicates the direction or path along which an entity moves or is moving relative to a reference frame or point.
-
E.
movementCause
Indicates that one entity’s action or event is the cause of another entity’s movement or change in location.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1e98900819092c54c0fb58b958a |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.