Triple
T19141775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadab |
E468575
|
entity |
| Predicate | scriptureCharacterType |
P134582
|
FINISHED |
| Object | monarch in the Deuteronomistic history |
—
|
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: monarch in the Deuteronomistic history | Statement: [Nadab, scriptureCharacterType, monarch in the Deuteronomistic history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptureCharacterType Context triple: [Nadab, scriptureCharacterType, monarch in the Deuteronomistic history]
-
A.
scriptureType
Indicates the classification or category of a scripture in relation to its type or genre.
-
B.
biblicalSourceCharacter
Indicates that one entity is the character or figure that serves as the source or origin for another entity within a biblical context.
-
C.
usesScriptureType
Indicates that one entity employs or is based on a particular type or classification of scripture.
-
D.
scripturalFeature
Indicates a relationship where something possesses or exhibits a characteristic, element, or quality specifically associated with scripture or sacred texts.
-
E.
helpsCharacterType
Indicates that one character type provides assistance or support to another character type.
- F. None of above. chosen
Provenance (4 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e975e09c8190911e98e6e558615d |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.