Triple
T2425066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St John Passion |
E53506
|
entity |
| Predicate | keyOpeningChorus |
P12877
|
FINISHED |
| Object | G minor |
—
|
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: G minor | Statement: [St John Passion, keyOpeningChorus, G minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOpeningChorus Context triple: [St John Passion, keyOpeningChorus, G minor]
-
A.
musicKey
chosen
Indicates the musical key in which a piece of music, passage, or section is composed or performed.
-
B.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
C.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
D.
keyPassage
Indicates that a specific passage or excerpt is identified as especially important, central, or representative within a larger text or discourse.
-
E.
keyVerse
Indicates that one verse is designated as the central or most thematically important verse in relation to a text, passage, or concept.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9f342e88190a430b02842ded418 |
completed | March 7, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69abc5a889948190b77de4ef6ac815a8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:42 p.m.