Triple
T18186945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shady Grove |
E435437
|
entity |
| Predicate | hasUnknownSongwriter |
P130145
|
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: [Shady Grove, hasUnknownSongwriter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnknownSongwriter Context triple: [Shady Grove, hasUnknownSongwriter, true]
-
A.
hasUnknownLyricist
Indicates that the lyricist associated with a work is not known or cannot be identified.
-
B.
containsSongWrittenBy
Indicates that an entity (such as an album, playlist, or collection) includes at least one song that was written by a specified creator or songwriter.
-
C.
hasPrimarySongwriter
Indicates that one entity serves as the main or principal songwriter responsible for creating the songs associated with another entity.
-
D.
hasUnknownAuthor
Indicates that the author of the entity is not known or cannot be identified.
-
E.
coveredSongBy
Indicates that one musical work is a cover version performed or recorded by an artist of a song originally created or popularized by another artist.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffe9e8081909c6bff40bbd279d2 |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:31 a.m.