Triple
T29068983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaky Shaky |
E735760
|
entity |
| Predicate | danceTrendOrigin |
P163496
|
FINISHED |
| Object | Latin America |
—
|
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: Latin America | Statement: [Shaky Shaky, danceTrendOrigin, Latin America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceTrendOrigin Context triple: [Shaky Shaky, danceTrendOrigin, Latin America]
-
A.
danceOrigin
chosen
Indicates that one entity is the place, culture, or context where a particular dance style or form originally developed or emerged.
-
B.
associatedDanceTrend
Indicates a relationship where one entity is linked to, or commonly recognized as having, a particular dance trend connected with it.
-
C.
danceEra
Indicates the historical period or era during which a particular style or form of dance was prominent or originated.
-
D.
hasDanceInfluence
Indicates that one entity has contributed to shaping, inspiring, or affecting the dance style, technique, or choreography of another entity.
-
E.
typeOfDanceFeatured
Indicates the specific style or category of dance that is highlighted or showcased in a given 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 10:19 a.m.