Triple
T13726253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | For Your Glory |
E329660
|
entity |
| Predicate | chorusTheme |
P111319
|
FINISHED |
| Object | desire to be where God is |
—
|
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: desire to be where God is | Statement: [For Your Glory, chorusTheme, desire to be where God is]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chorusTheme Context triple: [For Your Glory, chorusTheme, desire to be where God is]
-
A.
chorusFeature
Indicates that one entity participates in or is highlighted within the chorus section of another entity, such as a song or musical piece.
-
B.
chorus
Indicates that multiple entities jointly produce or participate in a coordinated vocal or expressive performance, typically as a unified group.
-
C.
chorusFocus
Indicates that the primary attention or emphasis is placed on a chorus or group performance rather than on individual elements.
-
D.
chorusType
Indicates the specific kind or category of chorus associated with an entity (e.g., type of vocal ensemble or choral grouping).
-
E.
chorusDirector
Indicates that one entity serves as the director or leader of a chorus in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f63c1c8190a7d0b84f319aa99b |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:55 p.m.