Triple

T8567804
Position Surface form Disambiguated ID Type / Status
Subject Leap of Faith E202849 entity
Predicate hasSpiritualElement P6456 FINISHED
Object religious imagery 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: religious imagery | Statement: [Leap of Faith, hasSpiritualElement, religious imagery]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSpiritualElement
Context triple: [Leap of Faith, hasSpiritualElement, religious imagery]
  • A. hasSpiritualDimension chosen
    Indicates that something possesses or involves a non-material, spiritual, or transcendent aspect or quality.
  • B. hasRitualElements
    Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
  • C. hasSpiritualHead
    Indicates that one entity serves as the primary religious or spiritual leader or authority for another entity.
  • D. containsSupernaturalElement
    Indicates that the subject involves or features a supernatural, magical, or otherworldly element beyond normal natural laws.
  • E. hasSpiritualSource
    Indicates that something originates from, is derived from, or is fundamentally grounded in a spiritual or non-material source.
  • 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_69ca8327b0a881908606ff860713964d completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe9d5d4ac8190a4d74c88b872d0b7 completed March 31, 2026, 3:35 p.m.
PD Predicate disambiguation batch_69cbd11856048190a1ce4b83a38f6965 completed March 31, 2026, 1:50 p.m.
Created at: March 30, 2026, 6:21 p.m.