Triple
T10061363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donegal |
E212996
|
entity |
| Predicate | hasTraditionalMusicStyle |
P526
|
FINISHED |
| Object | Donegal fiddle style |
—
|
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: Donegal fiddle style | Statement: [Donegal, hasTraditionalMusicStyle, Donegal fiddle style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalMusicStyle Context triple: [Donegal, hasTraditionalMusicStyle, Donegal fiddle style]
-
A.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
-
B.
hasGuitarStyle
Indicates that an entity is associated with, characterized by, or performs using a particular style of guitar playing.
-
C.
includesMusicalStyle
Indicates that one entity encompasses, features, or incorporates a particular musical style as part of its content or character.
-
D.
hasSongStyle
Indicates that an entity possesses, is characterized by, or is associated with a particular style or genre of song.
-
E.
musicTradition
chosen
Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcfd1fc98819082ec3f2f91151955 |
completed | April 2, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:57 p.m.