Triple
T23872319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | And the glory of the Lord |
E592760
|
entity |
| Predicate | textSourceVerses |
P28117
|
FINISHED |
| Object | Isaiah 40:5 |
—
|
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: Isaiah 40:5 | Statement: [And the glory of the Lord, textSourceVerses, Isaiah 40:5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textSourceVerses Context triple: [And the glory of the Lord, textSourceVerses, Isaiah 40:5]
-
A.
containsVerse
chosen
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
B.
scriptureTextEnglish
Indicates that an entity’s associated scripture or sacred text is provided in the English language.
-
C.
neighboringVerseNext
Indicates that one verse directly follows another verse in sequence, making them adjacent neighbors in the text.
-
D.
usesVerseNumbers
Indicates that one entity organizes or references content using verse numbers associated with another entity.
-
E.
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.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbfed81881909905f71377f759b1 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.