Triple
T9117636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Who Would Imagine a King |
E218761
|
entity |
| Predicate | lyricsPerspective |
P4917
|
FINISHED |
| Object | contemplation of Mary about Jesus |
—
|
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: contemplation of Mary about Jesus | Statement: [Who Would Imagine a King, lyricsPerspective, contemplation of Mary about Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricsPerspective Context triple: [Who Would Imagine a King, lyricsPerspective, contemplation of Mary about Jesus]
-
A.
lyricalPerspective
chosen
Indicates the narrative or point of view from which lyrics are expressed in a song or vocal piece.
-
B.
featuresIntrospectiveLyrics
Indicates that the subject contains lyrics characterized by self-reflection, inner thought, or personal emotional examination.
-
C.
lyricFocus
Indicates that the primary emphasis or subject of the lyrics is centered on a particular entity or theme.
-
D.
lyricType
Indicates the specific category or role that a lyric plays within a musical or lyrical work (e.g., verse, chorus, bridge).
-
E.
lyricReference
Indicates that one entity (typically a work or text) contains or makes a reference to the lyrics of another entity.
- 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a5e2ac8190b602ef0c77deb2fa |
completed | April 1, 2026, 5:09 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.