Triple

T747683
Position Surface form Disambiguated ID Type / Status
Subject John Chrysostom E15378 entity
Predicate styleOfExegesis P18616 FINISHED
Object literal-historical interpretation 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: literal-historical interpretation | Statement: [John Chrysostom, styleOfExegesis, literal-historical interpretation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: styleOfExegesis
Context triple: [John Chrysostom, styleOfExegesis, literal-historical interpretation]
  • A. 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.
  • B. theologicalInterpretation
    Indicates a relationship where an event, text, or phenomenon is understood or explained through religious or doctrinal beliefs and principles.
  • C. 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.
  • D. scriptureType
    Indicates the classification or category of a scripture in relation to its type or genre.
  • E. inScripture
    Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
  • 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_69a49358aa308190adbc9b5a0a2adcf9 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a62dd1bc819094a3814654448ae3 completed March 1, 2026, 8:48 p.m.
PD Predicate disambiguation batch_69a4a4ff10608190bfd60b4a1cb38f7d completed March 1, 2026, 8:43 p.m.
PDg Predicate description generation batch_69a4a57267c481909790a1fda3fced08 completed March 1, 2026, 8:45 p.m.
Created at: March 1, 2026, 7:37 p.m.