Triple

T22159080
Position Surface form Disambiguated ID Type / Status
Subject Symphony No. 1 (Arnold) E547618 entity
Predicate performingForces P135323 FINISHED
Object symphony orchestra 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: symphony orchestra | Statement: [Symphony No. 1 (Arnold), performingForces, symphony orchestra]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: performingForces
Context triple: [Symphony No. 1 (Arnold), performingForces, symphony orchestra]
  • A. originalPerformanceForces chosen
    Indicates the specific instruments, voices, or ensembles for which a musical work was originally composed or intended to be performed.
  • B. typicalPerformanceForces
    Indicates the forces that are normally or characteristically exerted or experienced during a given type of performance or operation.
  • C. componentForces
    Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
  • D. ledForcesFrom
    Indicates that one entity commanded or directed military or armed forces originating from another entity or location.
  • E. typeOfForcesDirected
    Indicates that certain forces are oriented or directed toward a particular target, direction, or reference.
  • 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_69e11e3b52088190ad5df386d01eb2fb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f12a2b5b10819090630fbadacb67af completed April 28, 2026, 9:44 p.m.
PD Predicate disambiguation batch_69e71b41555881909b8e22718974d527 completed April 21, 2026, 6:37 a.m.
Created at: April 16, 2026, 8:33 p.m.