Triple
T2544828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deus Caritas Est |
E57873
|
entity |
| Predicate | keyBiblicalCitation |
P3661
|
FINISHED |
| Object | 1 John 4:8 |
—
|
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: 1 John 4:8 | Statement: [Deus Caritas Est, keyBiblicalCitation, 1 John 4:8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyBiblicalCitation Context triple: [Deus Caritas Est, keyBiblicalCitation, 1 John 4:8]
-
A.
keyVerse
Indicates that one verse is designated as the central or most thematically important verse in relation to a text, passage, or concept.
-
B.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
C.
numberInBiblicalText
Indicates that a specific number appears within, or is referenced by, a given passage or unit of biblical text.
-
D.
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.
-
E.
inScripture
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2c10ce88190b242ab3d41878fda |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.