Triple
T19784289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talmai, king of Geshur |
E475218
|
entity |
| Predicate | biblicalBookReference |
P11163
|
FINISHED |
| Object | 2 Samuel 3:3 |
—
|
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: 2 Samuel 3:3 | Statement: [Talmai, king of Geshur, biblicalBookReference, 2 Samuel 3:3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalBookReference Context triple: [Talmai, king of Geshur, biblicalBookReference, 2 Samuel 3:3]
-
A.
scripturalReference
Indicates that one entity cites, alludes to, or is based on a specific passage or portion of a scriptural text found in another entity.
-
B.
associatedBiblicalBook
Indicates that one entity is linked or connected to a specific book of the Bible as its relevant or referenced scriptural source.
-
C.
scriptureFor
Indicates that one entity serves as a scriptural or authoritative religious text for another entity (such as a person, group, or belief system).
-
D.
scripturalSection
Indicates a relationship where one text or passage is a specific section or subdivision within a larger scriptural work.
-
E.
inScripture
chosen
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65385ee8081908d58cc3ff05b9b23 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.