Triple
T19704611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrtha |
E473179
|
entity |
| Predicate | choreographicFeatures |
P132276
|
FINISHED |
| Object | large jumps |
—
|
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: large jumps | Statement: [Myrtha, choreographicFeatures, large jumps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: choreographicFeatures Context triple: [Myrtha, choreographicFeatures, large jumps]
-
A.
choreographicApproach
Indicates an artistic relationship where one entity defines or employs a particular method, style, or strategy for creating or organizing choreography in relation to another.
-
B.
choreographicElement
chosen
Indicates a relationship where one entity functions as a distinct movement, figure, or structural unit within a larger choreographic composition or dance sequence.
-
C.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
D.
danceFeature
Indicates that one entity serves as a notable characteristic, element, or attribute of a dance or dancing-related activity.
-
E.
hasChoreographyBasedOn
Indicates that one choreography is derived from, inspired by, or structured according to another existing work or source.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b998608190a82f23bbf77f7bd2 |
completed | April 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.