Triple
T34026672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aunt Mary |
E872524
|
entity |
| Predicate | mentionedInLyricsOf |
P114550
|
FINISHED |
| Object | Long Tall Sally |
—
|
NE NERFINISHED |
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: Long Tall Sally | Statement: [Aunt Mary, mentionedInLyricsOf, Long Tall Sally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionedInLyricsOf Context triple: [Aunt Mary, mentionedInLyricsOf, Long Tall Sally]
-
A.
hasLyricsMentioning
chosen
Indicates that the referenced lyrics explicitly mention or refer to the specified entity.
-
B.
hasWrittenLyricsFor
Indicates that one entity is the lyricist who has created the words for a song or musical work performed or associated with another entity.
-
C.
lyricallyPairedWith
Indicates that two musical or poetic elements are intentionally matched or combined in lyrics, such as being written to accompany each other or to form a complementary lyrical pair.
-
D.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
-
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.
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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.