Triple
T30606341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis 39 |
E779053
|
entity |
| Predicate | featuresDivineName |
P50397
|
FINISHED |
| Object | YHWH |
—
|
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: YHWH | Statement: [Genesis 39, featuresDivineName, YHWH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDivineName Context triple: [Genesis 39, featuresDivineName, YHWH]
-
A.
divineNameMeaning
Indicates that a specified divine name carries a particular meaning or interpretation.
-
B.
divineSign
Indicates that one entity serves as a supernatural or sacred omen, message, or signal from a divine source to another entity.
-
C.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
D.
featuresDeity
Indicates that a work, object, or context prominently includes, depicts, or centers around a particular deity.
-
E.
containsDivineName
chosen
Indicates that the referenced entity includes or explicitly mentions a divine or sacred name within its content.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: April 29, 2026, 8:25 p.m.