Triple
T33202110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pettai Rap |
E849927
|
entity |
| Predicate | hasDanceStyleAssociation |
P176803
|
FINISHED |
| Object | street 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: street dance | Statement: [Pettai Rap, hasDanceStyleAssociation, street dance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDanceStyleAssociation Context triple: [Pettai Rap, hasDanceStyleAssociation, street dance]
-
A.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
B.
hasDanceEnsemble
Indicates that an entity is associated with or includes a particular dance ensemble as part of its activities or composition.
-
C.
hasDanceMovement
Indicates that one entity includes, performs, or is characterized by a specific dance movement associated with another entity.
-
D.
hasDanceInfluence
Indicates that one entity has contributed to shaping, inspiring, or affecting the dance style, technique, or choreography of another entity.
-
E.
hasDancePosition
Indicates that one entity occupies or is assigned a specific position or role within a dance formation or choreography.
- F. None of above. chosen
Provenance (4 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6f37f36ac8190b1bff8711d6771cb |
completed | May 3, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:30 a.m.