Triple
T29507721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Síguelo Bailando |
E748556
|
entity |
| Predicate | hasChoreographyTheme |
P176379
|
FINISHED |
| Object | 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: dance | Statement: [Síguelo Bailando, hasChoreographyTheme, dance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChoreographyTheme Context triple: [Síguelo Bailando, hasChoreographyTheme, dance]
-
A.
hasChoreographyBasedOn
Indicates that one choreography is derived from, inspired by, or structured according to another existing work or source.
-
B.
hasChoreographicCharacteristics
Indicates that something possesses specific features, qualities, or attributes related to choreography or choreographic style.
-
C.
hasDanceTheme
chosen
Indicates that an entity features, is characterized by, or centers around a particular dance-related theme.
-
D.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
E.
choreographyIncludes
Indicates that a choreography or dance piece contains or incorporates a specific movement, sequence, or component as part of its structure.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 28, 2026, 4:29 p.m.