Triple
T1651844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesse |
E35709
|
entity |
| Predicate | roleInBible |
P27433
|
FINISHED |
| Object | Father of King David |
—
|
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: Father of King David | Statement: [Jesse, roleInBible, Father of King David]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBible Context triple: [Jesse, roleInBible, Father of King David]
-
A.
biblicalFigureRole
chosen
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
B.
theologicalRole
Indicates a relationship where an entity holds or is assigned a specific function, office, or status within a theological or religious framework.
-
C.
roleInSalvationHistory
Indicates the specific function or significance an entity has within the overarching narrative or process of salvation history.
-
D.
liturgicalRole
Indicates the specific function or position an entity holds within a religious or liturgical context.
-
E.
roleInJudaism
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaa0fbe984819084f8daee81ca9b67 |
completed | March 6, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69a907ce4dd881909168a1e99505d4ec |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.