Triple
T1481953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Every Little Step |
E30976
|
entity |
| Predicate | hasDanceChoreography |
P29261
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Every Little Step, hasDanceChoreography, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDanceChoreography Context triple: [Every Little Step, hasDanceChoreography, Yes]
-
A.
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.
-
B.
hasDanceQuality
Indicates that something possesses a particular characteristic or attribute related to dance, such as style, skill, or expressive quality.
-
C.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
D.
danceCreated
Indicates that one entity is the creator or choreographer of a particular dance or dance work.
-
E.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
- F. None of above. chosen
Provenance (4 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c6782f088190930d25a56161e2b3 |
completed | March 1, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c57984088190b2c2d2d9cc2e5df9 |
completed | March 1, 2026, 11:02 p.m. |
Created at: March 1, 2026, 8:11 p.m.