Triple

T6826513
Position Surface form Disambiguated ID Type / Status
Subject Thomas Sunday E157027 entity
Predicate hasPrimaryGospelReading P5456 FINISHED
Object John 20:19–31 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: John 20:19–31 | Statement: [Thomas Sunday, hasPrimaryGospelReading, John 20:19–31]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPrimaryGospelReading
Context triple: [Thomas Sunday, hasPrimaryGospelReading, John 20:19–31]
  • A. 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.
  • B. isGospelInfluenced
    Indicates that one entity (such as a work, style, or performance) is influenced in its characteristics, form, or content by gospel music or gospel traditions.
  • C. hasScripture
    Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
  • D. hasViewOnScripture
    Indicates that an entity holds a particular interpretive stance or doctrinal position regarding scripture.
  • E. hasSecondaryLiturgy
    Indicates that an entity is associated with an additional, subordinate liturgical service or rite beyond its primary liturgy.
  • 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_69c6882a5b5c8190917a7db9ed36bad1 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d58375248190935dd38d618994e3 completed March 27, 2026, 7:07 p.m.
PD Predicate disambiguation batch_69c6d09d95f0819091ca7f897dc21efe completed March 27, 2026, 6:46 p.m.
Created at: March 27, 2026, 2:18 p.m.