Triple
T34656641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoot |
E889999
|
entity |
| Predicate | danceAssociatedWithSong |
P86188
|
FINISHED |
| Object | Shoot dance |
—
|
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: Shoot dance | Statement: [Shoot, danceAssociatedWithSong, Shoot dance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceAssociatedWithSong Context triple: [Shoot, danceAssociatedWithSong, Shoot dance]
-
A.
hasDanceAssociation
chosen
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
B.
danceHit
Indicates that one entity is a popular or successful dance track, recognized as a hit in the context of dance music.
-
C.
danceCreated
Indicates that one entity is the creator or choreographer of a particular dance or dance work.
-
D.
danceFeature
Indicates that one entity serves as a notable characteristic, element, or attribute of a dance or dancing-related activity.
-
E.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
- 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_69f722c7fbf081909a592b688125a5e1 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.