Triple
T8726979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanit |
E207153
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Baal Hammon |
E38725
|
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: Baal Hammon | Statement: [Tanit, spouse, Baal Hammon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Baal Hammon Context triple: [Tanit, spouse, Baal Hammon]
-
A.
Baal
chosen
Baal is a prominent ancient Near Eastern storm and fertility god widely worshipped across Phoenician and Canaanite cultures.
-
B.
Baal
Baal is a 1918 expressionist play by Bertolt Brecht that follows the amoral, self-destructive life of a bohemian poet.
-
C.
Esh-baal
Esh-baal is a biblical figure, a son of King Saul who briefly ruled as king over Israel in opposition to David after Saul’s death.
-
D.
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.
-
E.
Pammon
Pammon is a lesser-known son of King Priam of Troy mentioned in Greek mythology as one of the many Trojan princes.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d16cba881908e2a14b60ae65524 |
completed | March 31, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf291b737481909a90e482273c5f76 |
completed | April 3, 2026, 2:42 a.m. |
Created at: March 30, 2026, 6:37 p.m.