Triple

T21555316
Position Surface form Disambiguated ID Type / Status
Subject Morning Has Broken E531875 entity
Predicate hasTuneOrigin P144224 FINISHED
Object Scottish Gaelic traditional melody 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: Scottish Gaelic traditional melody | Statement: [Morning Has Broken, hasTuneOrigin, Scottish Gaelic traditional melody]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTuneOrigin
Context triple: [Morning Has Broken, hasTuneOrigin, Scottish Gaelic traditional melody]
  • A. hasOriginalMusicBy
    Indicates that the original musical score or soundtrack for a work was created or composed by a specified entity.
  • B. tunedOrUntuned
    Indicates whether something is in a properly adjusted or calibrated state (tuned) or not (untuned).
  • C. hasRhythmOrigin
    Indicates that one rhythm, style, or rhythmic pattern originates from, is derived from, or has its roots in another source.
  • D. isTunedTo
    Indicates that one entity has been adjusted or configured to operate at, receive, or correspond to the frequency, channel, or setting of another entity.
  • E. containsOriginalSongs
    Indicates that one entity includes or features songs that are original compositions rather than covers or adaptations.
  • F. None of above. chosen

Provenance (4 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_69e0c460232c81908de2c3819d17c00e completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eed2df48c88190894b6b08a5cb6390 completed April 27, 2026, 3:07 a.m.
PD Predicate disambiguation batch_69e6320766308190ba5dca2f7c826aa4 completed April 20, 2026, 2:02 p.m.
PDg Predicate description generation batch_69e633bf34c481909925d8dc1a633a65 completed April 20, 2026, 2:10 p.m.
Created at: April 16, 2026, 6:29 p.m.