Triple
T19271535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rehoboth (biblical city) |
E481939
|
entity |
| Predicate | hasBiblicalVerse |
P5605
|
FINISHED |
| Object | Genesis 26:22 |
—
|
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: Genesis 26:22 | Statement: [Rehoboth (biblical city), hasBiblicalVerse, Genesis 26:22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiblicalVerse Context triple: [Rehoboth (biblical city), hasBiblicalVerse, Genesis 26:22]
-
A.
hasScripture
chosen
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
B.
hasVersesBy
Indicates a relationship where a work, such as a song or poem, contains verses authored or written by a specific creator.
-
C.
hasVersesIn
Indicates that one entity (typically a text, chapter, or section) contains or is composed of verses found within another entity (such as a book, collection, or scripture).
-
D.
containsVerse
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
E.
hasViewOnScripture
Indicates that an entity holds a particular interpretive stance or doctrinal position regarding scripture.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbb8bea08190b5c65eebe67dccbb |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.