Triple

T28298691
Position Surface form Disambiguated ID Type / Status
Subject Tenorissimo E713640 entity
Predicate workFeaturedPerformer P47593 FINISHED
Object Roberto Alagna 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: Roberto Alagna | Statement: [Tenorissimo, workFeaturedPerformer, Roberto Alagna]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: workFeaturedPerformer
Context triple: [Tenorissimo, workFeaturedPerformer, Roberto Alagna]
  • A. workFeaturedArtist chosen
    Indicates that a creative work includes a particular artist in a special or highlighted role (e.g., as a featured performer or collaborator).
  • B. workFeaturedActor
    Indicates that a particular actor is prominently featured in or plays a significant role in a given work (such as a film, show, or production).
  • C. performerNotableWork
    Indicates that a performer is significantly associated with or best known for a particular work (such as a performance, production, or recording).
  • D. featuresSoloPerformancesBy
    Indicates that the subject includes or showcases solo performances carried out by the specified performer or performers.
  • E. coPerformer
    Indicates that two or more entities jointly perform the same act or participate together in the same performance.
  • 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_69efb524ab688190a1ce7ee7c9520932 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f644b13498819095df64be37e48ae0 completed May 2, 2026, 6:38 p.m.
PD Predicate disambiguation batch_69f641e0fde08190bf06a1c5b388aa84 completed May 2, 2026, 6:26 p.m.
Created at: April 27, 2026, 11:34 p.m.