Triple
T27314995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimond |
E689314
|
entity |
| Predicate | hasNotableHymnTune |
P60491
|
FINISHED |
| Object | Crimond hymn tune |
—
|
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: Crimond hymn tune | Statement: [Crimond, hasNotableHymnTune, Crimond hymn tune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableHymnTune Context triple: [Crimond, hasNotableHymnTune, Crimond hymn tune]
-
A.
hasNoMusicalScore
Indicates that something lacks an associated musical score or written musical accompaniment.
-
B.
hasNotableMusicWork
Indicates that an entity is associated with a significant or well-known musical work, such as a composition, recording, or performance.
-
C.
hasNotableSongType
Indicates that an entity is associated with a specific type or category of notable song.
-
D.
hasNotableComposer
Indicates that an entity is associated with a composer who is recognized as particularly significant or distinguished.
-
E.
associatedWithHymns
chosen
Indicates that something has a connection or relationship to hymns, such as being used in, derived from, or thematically linked to them.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: April 27, 2026, 11:30 a.m.