Triple

T34789495
Position Surface form Disambiguated ID Type / Status
Subject Low Church Anglicanism E1002906 entity
Predicate hasTheologyType P100888 FINISHED
Object evangelical theology 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: evangelical theology | Statement: [Low Church Anglicanism, hasTheologyType, evangelical theology]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTheologyType
Context triple: [Low Church Anglicanism, hasTheologyType, evangelical theology]
  • A. typeOfTheology chosen
    Indicates the specific theological category, tradition, or system that characterizes a given religious belief, doctrine, or discourse.
  • B. hasTheologicalElement
    Indicates that something includes, expresses, or is characterized by a theological aspect, theme, or component.
  • C. hasTheologicalAnalysisComponent
    Indicates that something includes or is associated with a component involving theological analysis or examination.
  • D. hasTheologicalMethod
    Indicates a relationship where a subject employs, follows, or is characterized by a particular theological method or approach to doing theology.
  • E. hasReligiousType
    Indicates that an entity is associated with or classified under a particular religion or religious category.
  • 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_69f76db47d408190a24fc7164439ea2d completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f7979a073881909a4fde2558e6b6f3 completed May 3, 2026, 6:44 p.m.
PD Predicate disambiguation batch_69f7961550f88190b7bb8a9155458b54 completed May 3, 2026, 6:38 p.m.
Created at: May 3, 2026, 3:59 p.m.