Triple
T31213598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thriller (song) |
E795812
|
entity |
| Predicate | hasSignatureDance |
P29261
|
FINISHED |
| Object | Thriller dance |
—
|
NE NERFINISHED |
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: Thriller dance | Statement: [Thriller (song), hasSignatureDance, Thriller dance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureDance Context triple: [Thriller (song), hasSignatureDance, Thriller dance]
-
A.
hasDanceChoreography
chosen
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
B.
hasDanceMove
Indicates that an entity performs, demonstrates, or is associated with a particular dance move.
-
C.
hasDanceFormation
Indicates that an entity participates in or is arranged into a specific dance formation.
-
D.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
E.
hasDanceMovement
Indicates that one entity includes, performs, or is characterized by a specific dance movement associated with another entity.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 29, 2026, 9:09 p.m.