Triple

T33500022
Position Surface form Disambiguated ID Type / Status
Subject Divenire E857961 entity
Predicate hasOrchestralCollaboration P5979 FINISHED
Object true 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: true | Statement: [Divenire, hasOrchestralCollaboration, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOrchestralCollaboration
Context triple: [Divenire, hasOrchestralCollaboration, true]
  • A. hasOrchestralFeature
    Indicates that something includes, exhibits, or is characterized by a notable orchestral element or component.
  • B. performedWithOrchestra chosen
    Indicates that a performance or musical work was carried out in collaboration with an orchestra.
  • C. hasMelodicOrchestration
    Indicates that one entity provides or features the melodic orchestration for, or in association with, another entity.
  • D. musicOrchestratedBy
    Indicates that a piece of music or musical work is arranged or orchestrated by a specific person or entity.
  • E. isOrchestralWorkBy
    Indicates that a particular orchestral work was created or composed by a specified composer or artist.
  • 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_69f3497660508190a541826a81f7e9ab completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fe2f078c24819082ba396b56f02808 completed May 8, 2026, 6:44 p.m.
PD Predicate disambiguation batch_69fe228fe1988190baf3bb34897f3dbe completed May 8, 2026, 5:51 p.m.
Created at: May 1, 2026, 1:38 a.m.