Triple
T22089238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Coast Swing |
E545869
|
entity |
| Predicate | isTypicallyDancedTo |
P132277
|
FINISHED |
| Object | contemporary blues music |
—
|
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: contemporary blues music | Statement: [West Coast Swing, isTypicallyDancedTo, contemporary blues music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyDancedTo Context triple: [West Coast Swing, isTypicallyDancedTo, contemporary blues music]
-
A.
hasDanceableRhythm
Indicates that something possesses a rhythm or beat suitable for dancing.
-
B.
musicAndDance
Indicates a relationship where music is performed, accompanied by, or integrated with dance as a coordinated activity or event.
-
C.
hasDanceInfluence
Indicates that one entity has contributed to shaping, inspiring, or affecting the dance style, technique, or choreography of another entity.
-
D.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
E.
usedInDance
chosen
Indicates that something is employed or incorporated as a component or element within a dance performance or practice.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e47ba08190a208af72a7cc176f |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.