Triple
T19644966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lonesome Road |
E471649
|
entity |
| Predicate | isTraditionalSong |
P22735
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lonesome Road, isTraditionalSong, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTraditionalSong Context triple: [Lonesome Road, isTraditionalSong, true]
-
A.
includesTraditionalSong
Indicates that one entity contains or features a traditional song as part of its content or composition.
-
B.
isTraditionallySungBy
Indicates that something, typically a song or chant, is customarily performed vocally by a particular person, group, or type of performer according to tradition.
-
C.
isTraditional
chosen
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
D.
isPopularSongOf
Indicates that a song is widely liked, well-known, or frequently enjoyed in relation to a particular entity (such as an artist, album, or context).
-
E.
isPopularSongFrom
Indicates that a song is widely liked, well-known, or frequently played and originates from a particular source, such as an artist, album, or media 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6412452d481908b6946cad3c411d5 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.