Triple
T34635297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don't Blink |
E889404
|
entity |
| Predicate | containsLyricMotive |
P85363
|
FINISHED |
| Object | life passes quickly |
—
|
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: life passes quickly | Statement: [Don't Blink, containsLyricMotive, life passes quickly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsLyricMotive Context triple: [Don't Blink, containsLyricMotive, life passes quickly]
-
A.
lyricalMotive
Indicates a recurring musical or textual idea that serves as a unifying expressive element within a lyrical or vocal work.
-
B.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
-
C.
hasLyricsMentioning
Indicates that the referenced lyrics explicitly mention or refer to the specified entity.
-
D.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
E.
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.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a007ef69f5c8190be6fb89e918d30fa |
completed | May 10, 2026, 12:49 p.m. |
| PD | Predicate disambiguation | batch_6a007e4060448190ad7420b07c1fe219 |
completed | May 10, 2026, 12:46 p.m. |
Created at: May 1, 2026, 2:04 a.m.