Triple
T21557374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Moab |
E531928
|
entity |
| Predicate | otherDeity |
P7649
|
FINISHED |
| Object | Ashtar-Chemosh |
—
|
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: Ashtar-Chemosh | Statement: [Kingdom of Moab, otherDeity, Ashtar-Chemosh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashtar-Chemosh Context triple: [Kingdom of Moab, otherDeity, Ashtar-Chemosh]
-
A.
Astar-Chemosh
chosen
Astar-Chemosh is a syncretic Moabite deity combining aspects of the war god Chemosh with the astral or fertility characteristics associated with the goddess Astarte.
-
B.
Chemosh
Chemosh is the chief national god of the ancient Moabites, often linked with war, conquest, and sometimes child sacrifice in Near Eastern religious traditions.
-
C.
Chemosh-nadab
Chemosh-nadab was an ancient ruler of the kingdom of Moab, known from Near Eastern historical and epigraphic records.
-
D.
Baal
Baal is a prominent ancient Near Eastern storm and fertility god widely worshipped across Phoenician and Canaanite cultures.
-
E.
Baal
Baal is a powerful Prime Evil demon and one of the main antagonists in the Diablo video game series, known especially as the Lord of Destruction.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e04b048190ac3a9913094b4625 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 16, 2026, 6:29 p.m.