Triple
T3651877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Loco-Motion |
E77434
|
entity |
| Predicate | hasChoreography |
P29261
|
FINISHED |
| Object | simple line dance 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: simple line dance steps | Statement: [The Loco-Motion, hasChoreography, simple line dance steps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChoreography Context triple: [The Loco-Motion, hasChoreography, simple line dance steps]
-
A.
hasDanceChoreography
chosen
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
B.
hasDanceSequences
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
-
C.
choreographedIn
Indicates that an entity (typically a choreographer or group) created or arranged the choreography for a performance, work, or event in a specified context or production.
-
D.
hasDanceEnsemble
Indicates that an entity is associated with or includes a particular dance ensemble as part of its activities or composition.
-
E.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3b664448190986b5223d59de282 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.