Triple

T35282609
Position Surface form Disambiguated ID Type / Status
Subject Afro-Classic E1018973 entity
Predicate composerAdaptations P102761 FINISHED
Object classical compositions 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: classical compositions | Statement: [Afro-Classic, composerAdaptations, classical compositions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: composerAdaptations
Context triple: [Afro-Classic, composerAdaptations, classical compositions]
  • A. collaboratedOnAdaptationOf
    Indicates that two or more entities worked together on creating or producing an adaptation of an existing work.
  • B. adaptsWorkOf chosen
    Indicates that one entity modifies, transforms, or reinterprets the work created by another entity into a new form or context.
  • C. hasAdaptationsOfWorksIn
    Indicates that an entity includes or contains adaptations of works that originate from another specified entity or context.
  • D. adaptationCoauthor
    Indicates that the subject is a coauthor of an adaptation (e.g., a derivative or adapted work) based on another work.
  • E. adaptedWithin
    Indicates that one entity has been modified, adjusted, or tailored to function appropriately within the context, scope, or boundaries defined by another entity.
  • 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_69f76de6d39c8190bb11342e4b91ff2b completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fd9ff026a48190bfec33deeb3b2c43 completed May 8, 2026, 8:33 a.m.
PD Predicate disambiguation batch_69fd97d805bc8190ba12f429d3ad04c7 completed May 8, 2026, 7:59 a.m.
Created at: May 3, 2026, 4:03 p.m.