Triple
T16254232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deuteronomy 33:23 |
E394587
|
entity |
| Predicate | neighboringVerseNext |
P122361
|
FINISHED |
| Object | Deuteronomy 33:24 |
—
|
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: Deuteronomy 33:24 | Statement: [Deuteronomy 33:23, neighboringVerseNext, Deuteronomy 33:24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringVerseNext Context triple: [Deuteronomy 33:23, neighboringVerseNext, Deuteronomy 33:24]
-
A.
featuresAdditionalVersesBy
Indicates that a work includes extra or bonus verses contributed by another creator beyond the primary one.
-
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.
openingVerseTranslation
Indicates the specific translated rendering of the opening verse of a text or work.
-
D.
containsVerse
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
E.
usesVerseNumbers
Indicates that one entity organizes or references content using verse numbers associated with another entity.
- F. None of above. chosen
Provenance (4 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24598c9488190a92df7d8b1824724 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.