Triple
T23260118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swag Surfin' |
E581980
|
entity |
| Predicate | hasChoreographyFeature |
P88673
|
FINISHED |
| Object | side-to-side swaying in unison |
—
|
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: side-to-side swaying in unison | Statement: [Swag Surfin', hasChoreographyFeature, side-to-side swaying in unison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChoreographyFeature Context triple: [Swag Surfin', hasChoreographyFeature, side-to-side swaying in unison]
-
A.
hasChoreographyBasedOn
Indicates that one choreography is derived from, inspired by, or structured according to another existing work or source.
-
B.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
C.
hasChoreographicLegacy
Indicates that one entity has a lasting influence or recognized heritage in choreography that is derived from or shaped by another entity.
-
D.
hasDanceMovement
Indicates that one entity includes, performs, or is characterized by a specific dance movement associated with another entity.
-
E.
hasDanceMove
chosen
Indicates that an entity performs, demonstrates, or is associated with a particular dance move.
- 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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f194c7ec148190b01fd215a0c1daa1 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:11 p.m.