Triple
T28962181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Te Felicito |
E731929
|
entity |
| Predicate | includesDanceStyle |
P66999
|
FINISHED |
| Object | urban 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: urban dance | Statement: [Te Felicito, includesDanceStyle, urban dance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDanceStyle Context triple: [Te Felicito, includesDanceStyle, urban dance]
-
A.
hasDanceStyleAssociation
Indicates an association between an entity and a particular dance style with which it is related or connected.
-
B.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
C.
usesDanceForms
chosen
Indicates that one entity employs or incorporates specific dance forms in its actions, practices, or expressions.
-
D.
hasDancePopElements
Indicates that something incorporates stylistic or musical characteristics commonly associated with dance-pop.
-
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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: April 28, 2026, 8:50 a.m.