Triple
T29070105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sexy Movimiento |
E735790
|
entity |
| Predicate | hasDancingAssociated |
P102194
|
FINISHED |
| Object | reggaeton dancing |
—
|
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: reggaeton dancing | Statement: [Sexy Movimiento, hasDancingAssociated, reggaeton dancing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDancingAssociated Context triple: [Sexy Movimiento, hasDancingAssociated, reggaeton dancing]
-
A.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
B.
hasDanceMovement
chosen
Indicates that one entity includes, performs, or is characterized by a specific dance movement associated with another entity.
-
C.
hasDanceEnsemble
Indicates that an entity is associated with or includes a particular dance ensemble as part of its activities or composition.
-
D.
alsoDancedAs
Indicates that an entity performed under an additional dance name or identity besides their primary one.
-
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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 10:19 a.m.