Triple
T15724603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babylonian kingship ideology |
E381187
|
entity |
| Predicate | hasKeyDeity |
P7648
|
FINISHED |
| Object | Tashmetu |
E766894
|
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: Tashmetu | Statement: [Babylonian kingship ideology, hasKeyDeity, Tashmetu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tashmetu Context triple: [Babylonian kingship ideology, hasKeyDeity, Tashmetu]
-
A.
Tashmetu
chosen
Tashmetu is a Mesopotamian goddess associated with mercy and the granting of prayers, venerated alongside the god Nabu.
-
B.
Tashmetu-sharrat
Tashmetu-sharrat was a Neo-Assyrian queen and consort of King Sennacherib, known from royal inscriptions and administrative records of his reign.
-
C.
Seshemetka
Seshemetka was an early ancient Egyptian queen consort of the 1st Dynasty, known primarily as a wife of King Djer.
-
D.
Itaweret
Itaweret was an ancient Egyptian queen of the 12th Dynasty, known as the consort of Pharaoh Senusret II and likely the mother of his heir.
-
E.
Mut-Tuya
Mut-Tuya was an Egyptian queen of the 19th Dynasty, wife of Pharaoh Seti I and mother of Ramesses II.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb1fdd4819088f3e243263e5f73 |
completed | April 16, 2026, 2:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff82f8b88081909855d3da0346fa25 |
completed | May 9, 2026, 6:54 p.m. |
Created at: April 10, 2026, 4:46 a.m.