Triple
T2944209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sotavento |
E79460
|
entity |
| Predicate | hasDanceElement |
P13505
|
FINISHED |
| Object | percussive footwork |
—
|
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: percussive footwork | Statement: [Sotavento, hasDanceElement, percussive footwork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDanceElement Context triple: [Sotavento, hasDanceElement, percussive footwork]
-
A.
hasDanceSequences
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
-
B.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
C.
hasDanceQuality
chosen
Indicates that something possesses a particular characteristic or attribute related to dance, such as style, skill, or expressive quality.
-
D.
hasTraditionalDance
Indicates that an entity is associated with, practices, or possesses a specific traditional dance.
-
E.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b0db5081908e84def20a5e4a2d |
completed | March 8, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.