Triple

T28859699
Position Surface form Disambiguated ID Type / Status
Subject Prince of Peace E728824 entity
Predicate derivedFromScriptureVerse P3661 FINISHED
Object Isaiah 9:6 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: Isaiah 9:6 | Statement: [Prince of Peace, derivedFromScriptureVerse, Isaiah 9:6]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: derivedFromScriptureVerse
Context triple: [Prince of Peace, derivedFromScriptureVerse, Isaiah 9:6]
  • A. scripturalReference chosen
    Indicates that one entity cites, alludes to, or is based on a specific passage or portion of a scriptural text found in another entity.
  • B. 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).
  • C. hasScripture
    Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
  • D. inScripture
    Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
  • E. scriptureFor
    Indicates that one entity serves as a scriptural or authoritative religious text for another entity (such as a person, group, or belief system).
  • 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_69f031a01cbc8190ba87270bb6fe4639 completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f67d3624248190a36a9b2d2e9778d4 completed May 2, 2026, 10:39 p.m.
PD Predicate disambiguation batch_69f678ce54b081908c26edfd49e39c60 completed May 2, 2026, 10:21 p.m.
Created at: April 28, 2026, 6:46 a.m.