Triple
T9041318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'll See You in My Dreams |
E216634
|
entity |
| Predicate | hasLyricMotif |
P85363
|
FINISHED |
| Object | dreams as reunion |
—
|
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: dreams as reunion | Statement: [I'll See You in My Dreams, hasLyricMotif, dreams as reunion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLyricMotif Context triple: [I'll See You in My Dreams, hasLyricMotif, dreams as reunion]
-
A.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
B.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
-
C.
hasLyricsTone
Indicates the tonal quality or emotional character expressed by the lyrics of a piece of music.
-
D.
hasLyricPhrase
chosen
Indicates that one entity (typically a song or musical work) contains or is associated with a specific lyric phrase as part of its textual content.
-
E.
hasLyricalForm
Indicates that one entity (typically a musical or poetic work) possesses or is characterized by a particular lyrical structure or form.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b110fcc8190a09e8ac5d98e399e |
completed | April 1, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.