Triple
T10431303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Get Me Bodied |
E245918
|
entity |
| Predicate | hasAssociatedDanceRoutine |
P29261
|
FINISHED |
| Object | Get Me Bodied dance routine |
—
|
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: Get Me Bodied dance routine | Statement: [Get Me Bodied, hasAssociatedDanceRoutine, Get Me Bodied dance routine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedDanceRoutine Context triple: [Get Me Bodied, hasAssociatedDanceRoutine, Get Me Bodied dance routine]
-
A.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
B.
hasDanceChoreography
chosen
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
C.
hasDanceMove
Indicates that an entity performs, demonstrates, or is associated with a particular dance move.
-
D.
hasDanceSequences
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
-
E.
hasDanceSceneWith
Indicates that two entities participate together in a dance scene within the same context or 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea63f03c81908331655241102725 |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfbc546881908f312c66ee195f79 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:13 p.m.