Triple
T1950741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Davidic dynasty |
E42150
|
entity |
| Predicate | hasCovenant |
P531
|
FINISHED |
| Object | God of Israel |
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: God of Israel | Statement: [King Davidic dynasty, hasCovenant, God of Israel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: God of Israel Context triple: [King Davidic dynasty, hasCovenant, God of Israel]
-
A.
God
God is the supreme, all-powerful and all-knowing divine being who creates, sustains, and governs the universe in the biblical tradition.
-
B.
חַוָּה
חַוָּה is the Hebrew name of Eve, the first woman in the biblical creation narrative in the Book of Genesis.
-
C.
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.
-
D.
Shaddai
Shaddai is a Hebrew name for God, often associated with divine protection and power in Jewish tradition.
-
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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adfbc3cf6881909d42a04be18c3c73 |
completed | March 8, 2026, 10:44 p.m. |
Created at: March 4, 2026, 7:36 p.m.