Triple
T23145655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morning Has Broken |
E577577
|
entity |
| Predicate | tuneOrigin |
P144224
|
FINISHED |
| Object | Scottish Gaelic 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 melody | Statement: [Morning Has Broken, tuneOrigin, Scottish Gaelic melody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tuneOrigin Context triple: [Morning Has Broken, tuneOrigin, Scottish Gaelic melody]
-
A.
hasTuneOrigin
chosen
Indicates that one entity’s tune or melody originates from, is derived from, or is based on another entity.
-
B.
tunedBy
Indicates that one entity has been adjusted or calibrated in its settings, parameters, or configuration by another entity.
-
C.
tunedOrUntuned
Indicates whether something is in a properly adjusted or calibrated state (tuned) or not (untuned).
-
D.
tuning
Indicates the adjustment or calibration of something’s parameters or settings to achieve desired performance or behavior.
-
E.
usesTuneOf
Indicates that one work is created to be performed with, or is based on, the melody or musical setting originally belonging to another work.
- 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ece211c81908b53e98f0acae09a |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.