Triple

T34334709
Position Surface form Disambiguated ID Type / Status
Subject Abdelazer, or The Moor's Revenge E881112 entity
Predicate hasIncidentalMusicWork P127198 FINISHED
Object Abdelazer, Z 570 NE NERFINISHED

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: Abdelazer, Z 570 | Statement: [Abdelazer, or The Moor's Revenge, hasIncidentalMusicWork, Abdelazer, Z 570]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasIncidentalMusicWork
Context triple: [Abdelazer, or The Moor's Revenge, hasIncidentalMusicWork, Abdelazer, Z 570]
  • A. hasInstrumentalPerformer
    Indicates that an action, event, or work is performed or carried out by an entity serving as its instrumental performer.
  • B. hasNotableMusicWork
    Indicates that an entity is associated with a significant or well-known musical work, such as a composition, recording, or performance.
  • C. isMusicalWork
    Indicates that one entity is a musical composition or piece created as an artistic work.
  • D. hasMusicalWorkType
    Indicates that a musical work is associated with a specific type or category of musical composition.
  • E. hasSoundtrackWork chosen
    Indicates that one entity (typically a media product or work) includes or is associated with another entity that serves as its soundtrack or musical score.
  • 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_69f349ba96a08190b94887bae2d8ee49 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_6a001cc0ff588190bb7c8a6fd427d02b completed May 10, 2026, 5:50 a.m.
PD Predicate disambiguation batch_6a001b3ea18c8190aeda7a32b2697490 completed May 10, 2026, 5:44 a.m.
Created at: May 1, 2026, 1:58 a.m.