Triple
T19014353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lazarus’ Tomb |
E465306
|
entity |
| Predicate | linkedGospelChapter |
P111153
|
FINISHED |
| Object | John 11 |
—
|
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 11 | Statement: [Lazarus’ Tomb, linkedGospelChapter, John 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedGospelChapter Context triple: [Lazarus’ Tomb, linkedGospelChapter, John 11]
-
A.
associatedWithBiblicalChapter
chosen
Indicates that something has a specified connection or linkage to a particular chapter in the Bible.
-
B.
chapterAndVerse
Indicates a relationship where a specific chapter is associated with a specific verse (or set of verses) within a structured text, such as a book or document.
-
C.
linkedToGospel
Indicates a relationship where something is connected or related to the gospel, typically in content, origin, or thematic focus.
-
D.
neighboringVerseNext
Indicates that one verse directly follows another verse in sequence, making them adjacent neighbors in the text.
-
E.
neighboringVersePrevious
Indicates that one verse immediately precedes another verse in sequence, making it the previous neighboring verse.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6aac4dc8190ac51f22c13f1b96c |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.