Triple

T6891004
Position Surface form Disambiguated ID Type / Status
Subject All Saints E159043 entity
Predicate hasLiturgicalProper P5456 FINISHED
Object proper readings 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: proper readings | Statement: [All Saints, hasLiturgicalProper, proper readings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLiturgicalProper
Context triple: [All Saints, hasLiturgicalProper, proper readings]
  • A. hasLiturgicalNature
    Indicates that something possesses a liturgical character or function, typically relating to formal religious worship or rites.
  • B. hasLiturgicalContext
    Indicates that something is associated with, used in, or relevant to a formal religious or liturgical setting or practice.
  • C. hasLiturgicalExpression
    Indicates that one entity expresses, embodies, or is manifested through the liturgical practices, rites, or worship forms of another entity.
  • D. hasLiturgicalMention
    Indicates that one entity is referenced or mentioned within the liturgical texts, practices, or rites associated with another entity.
  • E. hasLiturgicalReading chosen
    Indicates that a religious service, observance, or liturgical event includes or is associated with a specific prescribed reading from scripture or other sacred text.
  • 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_69c6883568c8819081db6407e892cccc completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d92d45f08190a730b3842c95b521 completed March 27, 2026, 7:23 p.m.
PD Predicate disambiguation batch_69c6d7b53e9881909ec298daa9f1913b completed March 27, 2026, 7:17 p.m.
Created at: March 27, 2026, 2:24 p.m.