Triple
T8961803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Ishtar of Nineveh |
E214022
|
entity |
| Predicate | worshippedDeityCulture |
P85900
|
FINISHED |
| Object | Akkadian |
—
|
LITERAL 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: Akkadian | Statement: [Temple of Ishtar of Nineveh, worshippedDeityCulture, Akkadian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshippedDeityCulture Context triple: [Temple of Ishtar of Nineveh, worshippedDeityCulture, Akkadian]
-
A.
worshippedIn
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
-
B.
worshippedAs
Indicates that one entity is regarded and treated with religious reverence or devotion by another entity.
-
C.
deityCategory
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
D.
worshipedAs
Indicates that one entity regards and treats another as a deity or sacred figure, offering reverence, devotion, or religious honor.
-
E.
sharesDeitiesWith
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
- F. None of above. chosen
Provenance (4 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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6748baa88190ac54e701dc4d6212 |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7 p.m.