Triple
T10810011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Father Mapple |
E255071
|
entity |
| Predicate | biblicalTheme |
P13857
|
FINISHED |
| Object | obedience to 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: obedience to God | Statement: [Father Mapple, biblicalTheme, obedience to God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalTheme Context triple: [Father Mapple, biblicalTheme, obedience to God]
-
A.
scripturalTheme
chosen
Indicates that one entity represents a central religious or theological theme expressed, discussed, or emphasized within a scriptural text or passage.
-
B.
covenantalTheme
Indicates a recurring, binding relational pattern or motif structured like a covenantal agreement between parties.
-
C.
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).
-
D.
scriptureFocus
Indicates that something centers on, emphasizes, or is primarily concerned with religious scripture or sacred texts.
-
E.
hasReligiousTheme
Indicates that something (such as a work, event, or object) centrally involves or expresses religious ideas, symbols, practices, or narratives.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733b6efc48190bb64b5a8fac843c4 |
completed | April 9, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:18 p.m.