Triple
T2639870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evangelical Presbyterian Church |
E62837
|
entity |
| Predicate | viewOnBible |
P2324
|
FINISHED |
| Object | inspired Word of God |
—
|
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: inspired Word of God | Statement: [Evangelical Presbyterian Church, viewOnBible, inspired Word of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnBible Context triple: [Evangelical Presbyterian Church, viewOnBible, inspired Word of God]
-
A.
hasViewOnScripture
chosen
Indicates that an entity holds a particular interpretive stance or doctrinal position regarding scripture.
-
B.
inScripture
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
-
C.
scriptureFocus
Indicates that something centers on, emphasizes, or is primarily concerned with religious scripture or sacred texts.
-
D.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
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_69ab4c3f2dcc819082df80f5e032f690 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abd8fafad08190939b08558fea6abd |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.