Triple
T20516540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schäfflertanz |
E503696
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional Bavarian folk dance |
C1135
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: traditional Bavarian folk dance Context triple: [Schäfflertanz, instanceOf, traditional Bavarian folk dance]
-
A.
Georgian folk dance
Georgian folk dance is a traditional performing art from Georgia characterized by dynamic footwork, acrobatic movements, and expressive storytelling that reflects the country’s regional cultures and history.
-
B.
traditional dance
chosen
A traditional dance is a culturally rooted form of movement and expression passed down through generations, often performed during rituals, celebrations, or community gatherings to preserve and convey shared heritage and values.
-
C.
regional folk tradition
A regional folk tradition is a set of locally rooted customs, stories, practices, and expressions passed down through generations that reflect the shared history, values, and identity of a specific geographic community.
-
D.
Azerbaijani folk dance
Azerbaijani folk dance is a traditional performance art form characterized by energetic footwork, expressive hand and arm movements, and vibrant costumes that reflect the diverse regional cultures and historical heritage of Azerbaijan.
-
E.
Baroque dance
Baroque dance is a highly stylized form of 17th- and early 18th-century court and theatrical dance characterized by intricate step patterns, formalized gestures, and close integration with Baroque music and social etiquette.
- F. None of above.
Provenance (1 batch)
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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:36 a.m.