Triple
T9642048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 8 in D minor |
E233095
|
entity |
| Predicate | numberInComposerOutput |
P32662
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Symphony No. 8 in D minor, numberInComposerOutput, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInComposerOutput Context triple: [Symphony No. 8 in D minor, numberInComposerOutput, 8]
-
A.
workNumberInComposerOutput
chosen
Indicates that a specific work number appears in the output or catalog produced by a particular composer.
-
B.
positionInComposerOutput
Indicates that one entity occupies a specific position or index within the ordered output produced by a composer.
-
C.
numberInInstrument
Indicates that an entity specifies the count or quantity of items contained within or associated with a particular instrument.
-
D.
workNumberInHaydnOutput
Indicates the ordinal number assigned to a specific work within the catalog of Haydn’s compositions.
-
E.
coComposer
Indicates a relationship where two or more entities jointly compose a musical or artistic work together.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b566a2881909ab3f9502b1c3c8d |
completed | April 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:12 p.m.