Triple
T9058151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livin' on a Prayer |
E217055
|
entity |
| Predicate | chorusLyric |
P41008
|
FINISHED |
| Object | Whoa, we're halfway there |
—
|
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: Whoa, we're halfway there | Statement: [Livin' on a Prayer, chorusLyric, Whoa, we're halfway there]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chorusLyric Context triple: [Livin' on a Prayer, chorusLyric, Whoa, we're halfway there]
-
A.
lyricReference
Indicates that one entity (typically a work or text) contains or makes a reference to the lyrics of another entity.
-
B.
lyricalPhrase
chosen
Indicates that one entity is a lyrical phrase or line that is part of, derived from, or associated with another entity such as a song, poem, or musical work.
-
C.
chorus
Indicates that multiple entities jointly produce or participate in a coordinated vocal or expressive performance, typically as a unified group.
-
D.
lyricSetting
Indicates that one entity serves as the text or lyrics that are set to music or otherwise musically realized by another entity.
-
E.
lyricFocus
Indicates that the primary emphasis or subject of the lyrics is centered on a particular entity or theme.
- 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_69ca83d4425481909a319dab847724ec |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7ec808bc8190957b80820d98fd5b |
completed | April 1, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee6d83c819095d8ed0779aa8511 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:10 p.m.