Triple

T19681270
Position Surface form Disambiguated ID Type / Status
Subject Church of St. Adalbert (Mikołów) E472593 entity
Predicate hasLiturgicalServices P5314 FINISHED
Object Holy Mass 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: Holy Mass | Statement: [Church of St. Adalbert (Mikołów), hasLiturgicalServices, Holy Mass]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLiturgicalServices
Context triple: [Church of St. Adalbert (Mikołów), hasLiturgicalServices, Holy Mass]
  • A. hasWorshipServices
    Indicates that an entity conducts or provides organized religious worship services.
  • B. hasLiturgicalCelebration
    Indicates that a religious figure, event, or concept is formally commemorated or observed within a liturgical calendar or worship service.
  • C. liturgicalServices chosen
    Indicates that one entity conducts, provides, or is associated with formal acts of public worship or religious rites for another entity or context.
  • D. hasLiturgicalChurch
    Indicates that one entity is associated with, served by, or belongs to a particular liturgical church as its religious institution.
  • E. hasLiturgicalLife
    Indicates that an entity participates in or maintains practices, rituals, and rhythms associated with liturgical worship.
  • 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_69d8e514f2e08190ba70a4449519d218 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e641bf97348190bc31b00ed4ec6cad completed April 20, 2026, 3:09 p.m.
PD Predicate disambiguation batch_69e53039ea808190a9106a53f564ab92 completed April 19, 2026, 7:42 p.m.
Created at: April 10, 2026, 1:45 p.m.