Triple
T917727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaddai |
E19806
|
entity |
| Predicate | relatedNameOfGod |
P22343
|
FINISHED |
| Object | Adonai |
E108211
|
NE 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: Adonai | Statement: [Shaddai, relatedNameOfGod, Adonai]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adonai Context triple: [Shaddai, relatedNameOfGod, Adonai]
-
A.
YHWH
chosen
YHWH is the personal name of the God of Israel in the Hebrew Bible, regarded as the supreme, covenant-making and covenant-keeping deity in Jewish and Christian traditions.
-
B.
חַוָּה
חַוָּה is the Hebrew name of Eve, the first woman in the biblical creation narrative in the Book of Genesis.
-
C.
Shaddai
Shaddai is a Hebrew name for God, often associated with divine protection and power in Jewish tradition.
-
D.
Ohr Ein Sof
Ohr Ein Sof is a Kabbalistic term referring to the infinite, boundless divine light that emanates from the unknowable essence of God before any creation or limitation.
-
E.
Jebus
Jebus is the ancient Canaanite name for the city later known as Jerusalem.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b74b789c8190b174f9b17dc46f9e |
completed | March 1, 2026, 10:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a826d8f9408190aa286bb809507797 |
completed | March 4, 2026, 12:34 p.m. |
Created at: March 1, 2026, 7:40 p.m.