Triple
T30879715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haydn symphonies |
E786577
|
entity |
| Predicate | laterSymphonies |
P198878
|
FINISHED |
| Object | mature symphonies in four movements |
—
|
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: mature symphonies in four movements | Statement: [Haydn symphonies, laterSymphonies, mature symphonies in four movements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSymphonies Context triple: [Haydn symphonies, laterSymphonies, mature symphonies in four movements]
-
A.
oneOfLongestSymphonies
Indicates that the subject is among the longest symphonies in terms of duration or number of movements.
-
B.
numberOfSymphonies
Indicates the total count of symphonies associated with a given entity.
-
C.
isFinalSymphonyOf
Indicates that one symphony is the last or concluding symphony composed by a particular composer.
-
D.
secondSymphonyComposed
Indicates that an entity composed the second symphony associated with another entity (typically a composer and their second symphonic work).
-
E.
basedOnEarlierWorkBySameComposer
Indicates that a work is derived from, adapted from, or otherwise based on an earlier work created by the same composer.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
| PDg | Predicate description generation | batch_69ff10956d3881909144f880f92e90c4 |
completed | May 9, 2026, 10:46 a.m. |
Created at: April 29, 2026, 8:48 p.m.