Triple
T29513413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bat Seba |
E748719
|
entity |
| Predicate | hasBiblicalCharacters |
P137076
|
FINISHED |
| Object | Bathsheba |
—
|
NE NERFINISHED |
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: Bathsheba | Statement: [Bat Seba, hasBiblicalCharacters, Bathsheba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiblicalCharacters Context triple: [Bat Seba, hasBiblicalCharacters, Bathsheba]
-
A.
biblicalSourceCharacter
Indicates that one entity is the character or figure that serves as the source or origin for another entity within a biblical context.
-
B.
hasBiblicalConnection
Indicates a relationship in which one entity is connected to another through references, themes, origins, or influences derived from the Bible.
-
C.
hasOldTestamentFigurePresent
chosen
Indicates that an Old Testament figure is present or involved in the given context or situation.
-
D.
hasHumanCharacters
Indicates that the subject includes or features characters that are human beings.
-
E.
associatedBiblicalFigure
Indicates that one entity is linked or connected to a particular biblical figure, such as by reference, attribution, or traditional association.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 4:34 p.m.