Triple

T430844
Position Surface form Disambiguated ID Type / Status
Subject Easter Vigil E9707 entity
Predicate scripturalTheme P13857 FINISHED
Object salvation history 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: salvation history | Statement: [Easter Vigil, scripturalTheme, salvation history]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scripturalTheme
Context triple: [Easter Vigil, scripturalTheme, salvation history]
  • A. scripturalBasis
    Indicates that one entity serves as the religious or scriptural foundation, support, or justification for another entity (such as a belief, practice, or doctrine).
  • B. scripturalAllusion
    Indicates that one entity references, echoes, or draws upon content, themes, or language from a scriptural or sacred text in relation to another entity.
  • C. scriptureFor
    Indicates that one entity serves as a scriptural or authoritative religious text for another entity (such as a person, group, or belief system).
  • D. scriptureType
    Indicates the classification or category of a scripture in relation to its type or genre.
  • E. scriptureAllusion
    Indicates that one entity makes reference to, echoes, or is inspired by a passage, theme, or element from a scriptural text found in another entity.
  • F. None of above. chosen

Provenance (4 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_69a2e801e1d48190b505d1dd336b52ac completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2eeef065c81908ed30528a61da132 completed Feb. 28, 2026, 1:34 p.m.
PD Predicate disambiguation batch_69a2edd9264c8190b92f9a50348e5541 completed Feb. 28, 2026, 1:30 p.m.
PDg Predicate description generation batch_69a2eeb93584819082f23eff13e17c4f completed Feb. 28, 2026, 1:33 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.