Triple
T16432875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis 41 |
E399110
|
entity |
| Predicate | depictsRoleOfJoseph |
P27433
|
FINISHED |
| Object | Interpreter of dreams |
—
|
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: Interpreter of dreams | Statement: [Genesis 41, depictsRoleOfJoseph, Interpreter of dreams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsRoleOfJoseph Context triple: [Genesis 41, depictsRoleOfJoseph, Interpreter of dreams]
-
A.
depictsPersonRole
Indicates that an image or representation shows a person in a specific role, function, or capacity.
-
B.
biblicalFigureRole
chosen
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
C.
depictsSacrament
Indicates that one entity visually represents or portrays a religious sacrament associated with another entity.
-
D.
depictsFather
Indicates that one entity visually represents or portrays another entity in the role of a father.
-
E.
roleInJoshua
Indicates that an entity holds a specific role or function within the context of the Book of Joshua or its narrative events.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32b9f2e8c81909c60b8fb78255e5f |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.