Triple
T9068914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharks (West Side Story) |
E217311
|
entity |
| Predicate | danceStyleAssociated |
P36067
|
FINISHED |
| Object | Latin 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: Latin dance | Statement: [Sharks (West Side Story), danceStyleAssociated, Latin dance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danceStyleAssociated Context triple: [Sharks (West Side Story), danceStyleAssociated, Latin dance]
-
A.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
B.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
C.
associatedDanceTrend
chosen
Indicates a relationship where one entity is linked to, or commonly recognized as having, a particular dance trend connected with it.
-
D.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
E.
usesDanceForms
Indicates that one entity employs or incorporates specific dance forms in its actions, practices, or expressions.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc955ba250819085fa49e0059d06c1 |
completed | April 1, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:11 p.m.