Triple
T18633624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On Top of Old Smoky |
E455484
|
entity |
| Predicate | hasVariantLyrics |
P63839
|
FINISHED |
| Object | multiple traditional variants |
—
|
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: multiple traditional variants | Statement: [On Top of Old Smoky, hasVariantLyrics, multiple traditional variants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariantLyrics Context triple: [On Top of Old Smoky, hasVariantLyrics, multiple traditional variants]
-
A.
hasLyricalVariant
chosen
Indicates that one item has an alternative version that differs in its lyrics while remaining related to the original.
-
B.
hasVariableLyrics
Indicates that the lyrics of a song or musical piece change between different performances, versions, or contexts.
-
C.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
D.
hasLyricsFeature
Indicates that something possesses a particular characteristic or attribute related to its lyrics.
-
E.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fc74d208190bfda63b5b0b160cd |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.