Triple

T37397334
Position Surface form Disambiguated ID Type / Status
Subject Second Mass of Christmas (Roman Rite, traditional) E928888 entity
Predicate hasAgnusDei P188032 FINISHED
Object Agnus Dei of the chosen Mass ordinary 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: Agnus Dei of the chosen Mass ordinary | Statement: [Second Mass of Christmas (Roman Rite, traditional), hasAgnusDei, Agnus Dei of the chosen Mass ordinary]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAgnusDei
Context triple: [Second Mass of Christmas (Roman Rite, traditional), hasAgnusDei, Agnus Dei of the chosen Mass ordinary]
  • A. hasCanticle
    Indicates that an entity is associated with, contains, or is characterized by a specific canticle (a hymn or song of praise).
  • B. hasChoir
    Indicates that an entity possesses, maintains, or is associated with a choir.
  • C. hasChorusIn
    Indicates that a musical work includes a chorus section within the specified part or segment.
  • D. hasPlainchantCantusFirmus
    Indicates that something (typically a musical work or section) uses a plainchant melody as its cantus firmus foundation.
  • E. usesChorale
    Indicates that one entity incorporates or employs a chorale (a hymn-like musical piece) within its structure or content.
  • F. None of above. chosen

Provenance (4 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_69f76ebb10c481909b54b9dba263e29f completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb9e1845e881908d19158440cf3b87 completed May 6, 2026, 8:01 p.m.
PD Predicate disambiguation batch_69fb8d08d6988190a00794ac26078348 completed May 6, 2026, 6:48 p.m.
PDg Predicate description generation batch_69fb9e173f348190b7ab5935e4dca039 completed May 6, 2026, 8:01 p.m.
Created at: May 3, 2026, 4:16 p.m.