Triple
T33054207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deuteronomy 14:22–27 |
E845805
|
entity |
| Predicate | chapterVerseNotation |
P87263
|
FINISHED |
| Object | Deut 14:22–27 |
—
|
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: Deut 14:22–27 | Statement: [Deuteronomy 14:22–27, chapterVerseNotation, Deut 14:22–27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chapterVerseNotation Context triple: [Deuteronomy 14:22–27, chapterVerseNotation, Deut 14:22–27]
-
A.
chapterAndVerse
chosen
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.
verseNumber
Indicates the specific numbered position of a verse within an ordered sequence, such as in a chapter, song, or poem.
-
C.
hasVerseDivision
Indicates that a text or passage is organized into or associated with specific verse divisions.
-
D.
usesVerseNumbers
Indicates that one entity organizes or references content using verse numbers associated with another entity.
-
E.
scripturalChapters
Indicates that one entity is composed of, contains, or is divided into the specified scriptural chapters.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.