Triple
T38099120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reformed Episcopal Church |
E951326
|
entity |
| Predicate | orientationOnScripture |
P2324
|
FINISHED |
| Object | affirms the authority of Scripture |
—
|
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: affirms the authority of Scripture | Statement: [Reformed Episcopal Church, orientationOnScripture, affirms the authority of Scripture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orientationOnScripture Context triple: [Reformed Episcopal Church, orientationOnScripture, affirms the authority of Scripture]
-
A.
scriptureFocus
Indicates that something centers on, emphasizes, or is primarily concerned with religious scripture or sacred texts.
-
B.
hasViewOnScripture
chosen
Indicates that an entity holds a particular interpretive stance or doctrinal position regarding scripture.
-
C.
inScripture
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
-
D.
positionInScripture
Indicates the specific location or ordering of a passage, verse, or element within a scriptural text.
-
E.
scriptureApproach
Indicates the method, attitude, or interpretive framework with which an entity engages with or understands scripture.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.