Triple
T3720027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babylonian polytheism |
E81616
|
entity |
| Predicate | majorDeity |
P7648
|
FINISHED |
| Object | Adad |
E233608
|
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: Adad | Statement: [Babylonian polytheism, majorDeity, Adad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adad Context triple: [Babylonian polytheism, majorDeity, Adad]
-
A.
Adad
chosen
Adad is the Mesopotamian storm and rain god, associated with thunder, fertility, and divine judgment.
-
B.
Qadan
Qadan was a 13th-century Mongol military leader and prince of the Borjigin dynasty who led Mongol forces during their campaign in Poland.
-
C.
Avgad
Avgad is a variant form or textual tradition associated with the Jewish mystical work Temurah.
-
D.
Razihi
Razihi is a highly divergent Arabic-related language spoken by a small community in the mountainous Jabal Razih region of northwestern Yemen.
-
E.
Arakhin
Arakhin is a tractate of the Mishnah and Talmud that deals primarily with the laws of vows of valuation and consecration to the Temple.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca9b5ca8819094299fffc02606ce |
completed | March 8, 2026, 7:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4ce184c9c8190813ce589c48007c1 |
completed | March 14, 2026, 2:55 a.m. |
Created at: March 8, 2026, 3:34 p.m.