Triple
T18422391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary (The Wind Cries Mary) |
E442050
|
entity |
| Predicate | lyricalContext |
P45521
|
FINISHED |
| Object | post-argument reflection |
—
|
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: post-argument reflection | Statement: [Mary (The Wind Cries Mary), lyricalContext, post-argument reflection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricalContext Context triple: [Mary (The Wind Cries Mary), lyricalContext, post-argument reflection]
-
A.
lyricalPerspective
Indicates the narrative or point of view from which lyrics are expressed in a song or vocal piece.
-
B.
lyricalMotive
Indicates a recurring musical or textual idea that serves as a unifying expressive element within a lyrical or vocal work.
-
C.
lyricalPhrase
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.
-
D.
lyricalMood
chosen
Indicates the prevailing emotional tone or atmosphere conveyed through lyrics or vocal expression in a piece of music.
-
E.
lyricalEvent
Indicates an event or occurrence that is expressed, referenced, or described within the lyrics of a song.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a2c98b0819082672174bf69b88c |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.