Triple
T12297116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stop! In the Name of Love |
E293115
|
entity |
| Predicate | featuredDanceMove |
P88673
|
FINISHED |
| Object | stop hand gesture |
—
|
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: stop hand gesture | Statement: [Stop! In the Name of Love, featuredDanceMove, stop hand gesture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredDanceMove Context triple: [Stop! In the Name of Love, featuredDanceMove, stop hand gesture]
-
A.
typeOfDanceFeatured
Indicates the specific style or category of dance that is highlighted or showcased in a given context or work.
-
B.
danceFeature
Indicates that one entity serves as a notable characteristic, element, or attribute of a dance or dancing-related activity.
-
C.
hasDanceMove
chosen
Indicates that an entity performs, demonstrates, or is associated with a particular dance move.
-
D.
hasDanceMovement
Indicates that one entity includes, performs, or is characterized by a specific dance movement associated with another entity.
-
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.
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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:52 p.m.