Triple
T37611048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphonies by Johannes Brahms |
E935784
|
entity |
| Predicate | lastSymphony |
P92557
|
FINISHED |
| Object | Symphony No. 4 in E minor, Op. 98 |
—
|
NE NERFINISHED |
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: Symphony No. 4 in E minor, Op. 98 | Statement: [Symphonies by Johannes Brahms, lastSymphony, Symphony No. 4 in E minor, Op. 98]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastSymphony Context triple: [Symphonies by Johannes Brahms, lastSymphony, Symphony No. 4 in E minor, Op. 98]
-
A.
isFinalSymphonyOf
chosen
Indicates that one symphony is the last or concluding symphony composed by a particular composer.
-
B.
oneOfLongestSymphonies
Indicates that the subject is among the longest symphonies in terms of duration or number of movements.
-
C.
isLastOrchestralWorkOf
Indicates that the work is the final orchestral composition created by the specified composer or creator.
-
D.
lastConcertoComposed
Indicates that one entity is the final (most recently) composed concerto in the body of work of another entity.
-
E.
numberOfSymphonies
Indicates the total count of symphonies associated with a given entity.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.