Triple
T4768276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huldah |
E105863
|
entity |
| Predicate | scripturalGenreContext |
P6836
|
FINISHED |
| Object | 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: Deuteronomistic history | Statement: [Huldah, scripturalGenreContext, Deuteronomistic history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalGenreContext Context triple: [Huldah, scripturalGenreContext, Deuteronomistic history]
-
A.
scriptureContext
Indicates that one entity provides the textual, historical, or thematic scriptural background or setting necessary to interpret or understand another entity.
-
B.
scriptureType
chosen
Indicates the classification or category of a scripture in relation to its type or genre.
-
C.
scripturalAllusion
Indicates that one entity references, echoes, or draws upon content, themes, or language from a scriptural or sacred text in relation to another entity.
-
D.
scriptureAllusion
Indicates that one entity makes reference to, echoes, or is inspired by a passage, theme, or element from a scriptural text found in another entity.
-
E.
scripturalCorpus
Indicates that one entity is a body of scriptural or sacred texts associated with, or serving as the canonical writings for, another entity.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.