Triple
T25923047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eilean Eirisgeidh |
E653222
|
entity |
| Predicate | isFolkMusicOf |
P526
|
FINISHED |
| Object | Scotland |
—
|
NE NERFINISHED |
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: Scotland | Statement: [Eilean Eirisgeidh, isFolkMusicOf, Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFolkMusicOf Context triple: [Eilean Eirisgeidh, isFolkMusicOf, Scotland]
-
A.
isFolkSongFrom
Indicates that a folk song originates from or is traditionally associated with a particular place, region, or culture.
-
B.
hasFolkGenre
Indicates that something belongs to, is categorized under, or is associated with the folk music genre.
-
C.
musicTradition
chosen
Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
-
D.
stateFolkSong
Indicates that a particular folk song is officially associated with, or designated as belonging to, a specific state.
-
E.
musicalBasisFor
Indicates that one musical work, idea, or element serves as the foundational source or inspiration upon which another musical work, idea, or element is built or derived.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603eb73688190a260029e23d0731b |
completed | May 2, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:35 a.m.