Triple
T23872318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | And the glory of the Lord |
E592760
|
entity |
| Predicate | textSourceChapter |
P135864
|
FINISHED |
| Object | Isaiah 40 |
—
|
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 | Statement: [And the glory of the Lord, textSourceChapter, Isaiah 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textSourceChapter Context triple: [And the glory of the Lord, textSourceChapter, Isaiah 40]
-
A.
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.
-
B.
scripturalChapters
Indicates that one entity is composed of, contains, or is divided into the specified scriptural chapters.
-
C.
chapterOn
Indicates that one entity (typically a chapter) is about, discusses, or focuses on the subject represented by another entity.
-
D.
chapterMentioned
chosen
Indicates that a specific chapter is referenced or cited within a given context or source.
-
E.
sourceChapterNameMeaning
Indicates that a chapter’s name conveys or is associated with a particular meaning or interpretation.
- 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.