Triple
T35542440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Do the Funky Chicken |
E1027096
|
entity |
| Predicate | danceCrazeOfEra |
P113358
|
FINISHED |
| Object | late 1960s dance craze |
—
|
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: late 1960s dance craze | Statement: [Do the Funky Chicken, danceCrazeOfEra, late 1960s dance craze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceCrazeOfEra Context triple: [Do the Funky Chicken, danceCrazeOfEra, late 1960s dance craze]
-
A.
danceEra
Indicates the historical period or era during which a particular style or form of dance was prominent or originated.
-
B.
hasDanceCraze
chosen
Indicates that an entity is associated with, or is the origin of, a popular dance trend or fad.
-
C.
danceHit
Indicates that one entity is a popular or successful dance track, recognized as a hit in the context of dance music.
-
D.
musicAndDance
Indicates a relationship where music is performed, accompanied by, or integrated with dance as a coordinated activity or event.
-
E.
danceSceneInspired
Indicates that one dance scene is creatively influenced or modeled after another source, such as a different scene, style, or performance.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.