Triple
T34656374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Look Alive |
E889990
|
entity |
| Predicate | hasViralDance |
P113358
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Look Alive, hasViralDance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViralDance Context triple: [Look Alive, hasViralDance, true]
-
A.
hasDanceChallenge
Indicates that one entity presents, initiates, or is associated with a dance challenge involving another entity.
-
B.
hasViralMusicVideo
Indicates that an entity possesses or is associated with a music video that has achieved viral popularity or widespread online circulation.
-
C.
hasDanceCraze
chosen
Indicates that an entity is associated with, or is the origin of, a popular dance trend or fad.
-
D.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
E.
hasChoreographedDanceInVideo
Indicates that an entity has created or arranged the choreography for a dance that appears in a particular video.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 1, 2026, 2:04 a.m.