Triple
T2425078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St John Passion |
E53506
|
entity |
| Predicate | biblicalSourceChapters |
P5309
|
FINISHED |
| Object | John 18 |
—
|
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 18 | Statement: [St John Passion, biblicalSourceChapters, John 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalSourceChapters Context triple: [St John Passion, biblicalSourceChapters, John 18]
-
A.
scripturalSection
Indicates a relationship where one text or passage is a specific section or subdivision within a larger scriptural work.
-
B.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
C.
scripturalReference
Indicates that one entity cites, alludes to, or is based on a specific passage or portion of a scriptural text found in another entity.
-
D.
associatedBiblicalBook
chosen
Indicates that one entity is linked or connected to a specific book of the Bible as its relevant or referenced scriptural source.
-
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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9f342e88190a430b02842ded418 |
completed | March 7, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69abc5a889948190b77de4ef6ac815a8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:42 p.m.