Triple
T8357739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Father of Lies |
E196720
|
entity |
| Predicate | relatedBiblicalPassage |
P3661
|
FINISHED |
| Object | John 8:44 |
—
|
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: John 8:44 | Statement: [Father of Lies, relatedBiblicalPassage, John 8:44]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedBiblicalPassage Context triple: [Father of Lies, relatedBiblicalPassage, John 8:44]
-
A.
associatedBiblicalBook
Indicates that one entity is linked or connected to a specific book of the Bible as its relevant or referenced scriptural source.
-
B.
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.
-
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.
hasBiblicalConnection
Indicates a relationship in which one entity is connected to another through references, themes, origins, or influences derived from the Bible.
-
E.
associatedBiblicalFigure
Indicates that one entity is linked or connected to a particular biblical figure, such as by reference, attribution, or traditional association.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804b57f88190907a4e4e389caf5f |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.