Triple

T11940217
Position Surface form Disambiguated ID Type / Status
Subject Symphony No. 2 in D major, Op. 36 E284154 entity
Predicate workOrderInComposerOutput P32662 FINISHED
Object early symphony 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: early symphony | Statement: [Symphony No. 2 in D major, Op. 36, workOrderInComposerOutput, early symphony]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: workOrderInComposerOutput
Context triple: [Symphony No. 2 in D major, Op. 36, workOrderInComposerOutput, early symphony]
  • A. workNumberInComposerOutput chosen
    Indicates that a specific work number appears in the output or catalog produced by a particular composer.
  • B. workPeriodInComposerOutput
    Indicates the time span during which a particular work appears within a composer’s overall output or creative career.
  • C. workComposer
    Indicates that one entity is the composer or creator of a musical or artistic work represented by the other entity.
  • D. workNumberInMozartOutput
    Indicates the ordinal work number assigned to a composition within the catalog of Mozart’s works.
  • E. basedOnWorkComposer
    Indicates that one work is derived from, adapted from, or otherwise created on the basis of another work by the specified composer.
  • 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_69d6ab2ce9c48190b5d39511b524f666 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903415d2481909d84e6727454b9fe completed April 10, 2026, 2:03 p.m.
PD Predicate disambiguation batch_69d8bb3af0188190bfb22be5c97b3349 completed April 10, 2026, 8:56 a.m.
Created at: April 8, 2026, 9:45 p.m.