Triple

T352381
Position Surface form Disambiguated ID Type / Status
Subject Lent E7469 entity
Predicate fastingObligation P6166 FINISHED
Object varies by denomination 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: varies by denomination | Statement: [Lent, fastingObligation, varies by denomination]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fastingObligation
Context triple: [Lent, fastingObligation, varies by denomination]
  • A. preparatoryFastBegins
    Indicates that a required period of fasting starts in preparation for a subsequent event, action, or ritual.
  • B. religiousRestriction chosen
    Indicates that one entity imposes, experiences, or is subject to limitations or rules based on religious beliefs or practices in relation to another entity or context.
  • C. obligationCondition
    Indicates that one situation or state serves as the condition under which an obligation for an entity becomes active or must be fulfilled.
  • D. isNotRequiredFor
    Indicates that one entity is not necessary or mandatory for the existence, occurrence, validity, or completion of another entity or process.
  • E. waterRequirement
    Indicates the amount or conditions of water needed for an entity to grow, function, or be maintained properly.
  • 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_69a2e7e696948190bebc966535995e45 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eb7f1be88190964ddcbb6a05f021 completed Feb. 28, 2026, 1:19 p.m.
PD Predicate disambiguation batch_69a2e9571bd88190b6fcb16f21604720 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.