Triple
T23568108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resurrection Symphony |
E580024
|
entity |
| Predicate | usesChorusInMovements |
P84947
|
FINISHED |
| Object | fourth movement |
—
|
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: fourth movement | Statement: [Resurrection Symphony, usesChorusInMovements, fourth movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesChorusInMovements Context triple: [Resurrection Symphony, usesChorusInMovements, fourth movement]
-
A.
usesChorusBetweenStanzas
Indicates that a recurring chorus section is inserted between successive stanzas of a piece (such as a song or poem).
-
B.
usesChorale
Indicates that one entity incorporates or employs a chorale (a hymn-like musical piece) within its structure or content.
-
C.
hasChorusIn
chosen
Indicates that a musical work includes a chorus section within the specified part or segment.
-
D.
hasChorusBy
Indicates that something (typically a musical work or song) includes a chorus section that is performed, written, or provided by a specified entity.
-
E.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6e11008190bdd28c3f85e3004e |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:35 p.m.