Triple
T16877574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gloria |
E421337
|
entity |
| Predicate | hasChordProgression |
P40268
|
FINISHED |
| Object | E–D–A |
—
|
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: E–D–A | Statement: [Gloria, hasChordProgression, E–D–A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChordProgression Context triple: [Gloria, hasChordProgression, E–D–A]
-
A.
usesChordChangesOf
Indicates that one musical work employs the same or substantially similar chord progression as another work.
-
B.
tonalityProgression
chosen
Indicates a change or development in musical key or tonal center over the course of a piece or passage.
-
C.
hasVerseChorusStructure
Indicates that something, typically a musical composition, is organized using a recurring pattern of verses and choruses.
-
D.
hasChoralArrangement
Indicates that one entity is a choral arrangement version or setting of another entity (typically an original musical work).
-
E.
hasChorusHook
Indicates that a musical work features a prominent, recurring chorus section that serves as a memorable hook.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3b7f8a1d48190ad829f86e235a1d0 |
completed | April 18, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.