Triple
T25749122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teach Me How to Jerk |
E648422
|
entity |
| Predicate | danceTrend |
P36067
|
FINISHED |
| Object | YouTube jerkin' videos |
—
|
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: YouTube jerkin' videos | Statement: [Teach Me How to Jerk, danceTrend, YouTube jerkin' videos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceTrend Context triple: [Teach Me How to Jerk, danceTrend, YouTube jerkin' videos]
-
A.
associatedDanceTrend
chosen
Indicates a relationship where one entity is linked to, or commonly recognized as having, a particular dance trend connected with it.
-
B.
danceHit
Indicates that one entity is a popular or successful dance track, recognized as a hit in the context of dance music.
-
C.
musicAndDance
Indicates a relationship where music is performed, accompanied by, or integrated with dance as a coordinated activity or event.
-
D.
typeOfDanceFeatured
Indicates the specific style or category of dance that is highlighted or showcased in a given context or work.
-
E.
notableDance
Indicates that the subject is especially recognized or distinguished for a particular dance or dancing 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603bb02288190b40cedbed5b9651d |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 4:32 a.m.