Triple
T7727469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fisher’s Hornpipe |
E175168
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional fiddle tune |
C22760
|
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 fiddle tune Context triple: [Fisher’s Hornpipe, instanceOf, traditional fiddle tune]
-
A.
bagpipe tune
A bagpipe tune is a musical composition specifically written or arranged for the bagpipes, characterized by modal melodies, ornamented grace notes, and rhythmic patterns suited to the instrument’s continuous drone.
-
B.
traditional folk songs
Traditional folk songs are orally transmitted musical narratives or lyrical pieces that reflect the cultural identity, history, and everyday life of a community, evolving over generations through collective performance and adaptation.
-
C.
traditional musical instrument
A traditional musical instrument is a culturally rooted device, often handcrafted and passed down through generations, used to produce music that reflects the heritage and identity of a specific community or region.
-
D.
traditional jazz
Traditional jazz is a style of jazz rooted in early 20th-century New Orleans and swing-era practices, characterized by collective improvisation, acoustic instruments, and strong melodic and rhythmic foundations.
-
E.
mystical folk music tradition
A mystical folk music tradition is a culturally rooted musical practice that blends spiritual or esoteric themes with traditional instruments, melodies, and rituals to evoke a sense of enchantment and connection to the unseen.
- F. None of above. chosen
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_69c6995d541c81909eaa646b1a8369a9 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4:06 p.m.