Triple
T27596727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viennese waltz |
E699919
|
entity |
| Predicate | footwork |
P106635
|
FINISHED |
| Object | toe-heel for backward steps |
—
|
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: toe-heel for backward steps | Statement: [Viennese waltz, footwork, toe-heel for backward steps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footwork Context triple: [Viennese waltz, footwork, toe-heel for backward steps]
-
A.
dropFeet
Indicates that an entity lowers or places its feet down, typically from a raised or suspended position.
-
B.
footType
Indicates the specific kind or classification of feet that an entity possesses or is characterized by.
-
C.
feetFeature
chosen
Indicates that one entity has a specific characteristic, attribute, or notable aspect related to its feet.
-
D.
feetDirection
Indicates the orientation or direction in which an entity’s feet are pointing relative to a reference frame or another entity.
-
E.
feetGiveRiseTo
Indicates that the presence, condition, or movement of feet causes or brings about another state, event, or outcome.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:06 p.m.