Triple
T32291574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dum |
E824977
|
entity |
| Predicate | hasTraditionalDanceStyle |
P24698
|
FINISHED |
| Object | Dom 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: Dom dance | Statement: [Dum, hasTraditionalDanceStyle, Dom dance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalDanceStyle Context triple: [Dum, hasTraditionalDanceStyle, Dom dance]
-
A.
hasTraditionalDance
chosen
Indicates that an entity is associated with, practices, or possesses a specific traditional dance.
-
B.
hasChoreographicLegacy
Indicates that one entity has a lasting influence or recognized heritage in choreography that is derived from or shaped by another entity.
-
C.
recognizedAsClassicalDanceBy
Indicates that one entity is acknowledged or accepted by another entity as belonging to the tradition or category of classical dance.
-
D.
hasDanceInfluence
Indicates that one entity has contributed to shaping, inspiring, or affecting the dance style, technique, or choreography of another entity.
-
E.
hasDanceStyleAssociation
Indicates an association between an entity and a particular dance style with which it is related or connected.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 1, 2026, 12:44 a.m.