Triple
T15758851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimri-Lim |
E382039
|
entity |
| Predicate | patronDeity |
P5606
|
FINISHED |
| Object | Dagan |
E380648
|
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: Dagan | Statement: [Zimri-Lim, patronDeity, Dagan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dagan Context triple: [Zimri-Lim, patronDeity, Dagan]
-
A.
Dagan
chosen
Dagan is an ancient Northwest Semitic god, particularly revered by the Amorites and later in Mesopotamia, commonly associated with grain, fertility, and sometimes the underworld.
-
B.
Dadan
Dadan is an ancient North Arabian city and archaeological site, historically associated with the Dadanite and Lihyanite kingdoms in the Al-Ula region of northwestern Saudi Arabia.
-
C.
Zimran
Zimran is a lesser-known biblical figure mentioned in the Hebrew Bible as one of Abraham's sons by his wife Keturah.
-
D.
Dayan
Dayan is a Hebrew surname most famously associated with Israeli military leader and politician Moshe Dayan.
-
E.
Iddo
Iddo is a biblical figure mentioned in the Old Testament, known primarily as an ancestor of the prophet Zechariah and sometimes identified as a seer or priest.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b35ea48190a758ee76a57b5451 |
completed | April 16, 2026, 3 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff8774eda08190a6231b4fd5027e6f |
completed | May 9, 2026, 7:13 p.m. |
Created at: April 10, 2026, 4:47 a.m.