Triple

T18265337
Position Surface form Disambiguated ID Type / Status
Subject Great and Holy Monday E437468 entity
Predicate hasScriptureReadings P5456 FINISHED
Object Gospel passages about the fig tree 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: Gospel passages about the fig tree | Statement: [Great and Holy Monday, hasScriptureReadings, Gospel passages about the fig tree]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasScriptureReadings
Context triple: [Great and Holy Monday, hasScriptureReadings, Gospel passages about the fig tree]
  • A. scriptureRead
    Indicates that an entity reads, studies, or engages with a religious or sacred text.
  • B. hasViewOnScripture
    Indicates that an entity holds a particular interpretive stance or doctrinal position regarding scripture.
  • C. hasScripture
    Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
  • D. 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.
  • E. hasReading
    Indicates that an entity is associated with a particular reading, such as a measured value, interpretation, or recorded observation.
  • 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_69d8b913351c8190932b6a426de04b41 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ff79851481909a4bbeb14fb00647 completed April 19, 2026, 4:14 p.m.
PD Predicate disambiguation batch_69e44fcdee748190bae6fb76e0cb22f3 completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:34 a.m.