Triple
T30416392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rejoice in the Lamb |
E773767
|
entity |
| Predicate | firstPerformanceForces |
P135323
|
FINISHED |
| Object | parish church choir |
—
|
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: parish church choir | Statement: [Rejoice in the Lamb, firstPerformanceForces, parish church choir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceForces Context triple: [Rejoice in the Lamb, firstPerformanceForces, parish church choir]
-
A.
originalPerformanceForces
chosen
Indicates the specific instruments, voices, or ensembles for which a musical work was originally composed or intended to be performed.
-
B.
firstPerformanceBy
Indicates that the referenced performance is the earliest or debut performance carried out by the specified entity.
-
C.
firstPerformance
Indicates that an entity marks the initial or debut performance of another entity, such as a work, artist, or production.
-
D.
firstPerformanceTheatre
Indicates the theatre where an entity (such as a play or performance) was first performed.
-
E.
firstPerformanceAt
Indicates the location or event at which an entity (such as a work or performance) was first performed.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a021706e21c81909b83e2b4d9c4130c |
completed | May 11, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a0216861214819097d2177755bc19d7 |
completed | May 11, 2026, 5:48 p.m. |
Created at: April 29, 2026, 8:05 p.m.