Triple
T1920340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 1 "Jeremiah" |
E40110
|
entity |
| Predicate | hasVocalPartInMovement |
P33166
|
FINISHED |
| Object | Lamentation |
—
|
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: Lamentation | Statement: [Symphony No. 1 "Jeremiah", hasVocalPartInMovement, Lamentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVocalPartInMovement Context triple: [Symphony No. 1 "Jeremiah", hasVocalPartInMovement, Lamentation]
-
A.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
B.
hasVocalDuet
Indicates that two entities perform or participate together in a vocal duet.
-
C.
hasBackingVocals
Indicates that one musical performance, track, or part includes supporting vocal contributions accompanying a primary vocal line.
-
D.
partOfMusical
Indicates that something is a component, segment, or element belonging to a larger musical work or performance.
-
E.
hasVocalRangeDescription
Indicates that an entity is associated with a textual description of its vocal range or vocal capabilities.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb213af0481909429ec971860a3fd |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb1b180e481908bbe893d6ba6208b |
completed | March 7, 2026, 5:03 a.m. |
Created at: March 4, 2026, 7:35 p.m.