Triple
T15274292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power and the Glory |
E365096
|
entity |
| Predicate | hasLyricsForm |
P59491
|
FINISHED |
| Object | verse-chorus structure |
—
|
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: verse-chorus structure | Statement: [Power and the Glory, hasLyricsForm, verse-chorus structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLyricsForm Context triple: [Power and the Glory, hasLyricsForm, verse-chorus structure]
-
A.
hasLyricalForm
chosen
Indicates that one entity (typically a musical or poetic work) possesses or is characterized by a particular lyrical structure or form.
-
B.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
C.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
-
D.
hasLyricsFeature
Indicates that something possesses a particular characteristic or attribute related to its lyrics.
-
E.
hasLyricsTone
Indicates the tonal quality or emotional character expressed by the lyrics of a piece of music.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00952731c8190bf6a5e6e10c95b94 |
completed | April 15, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.