Triple
T14180168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebabbar |
E351430
|
entity |
| Predicate | deityRoleAtTemple |
P80423
|
FINISHED |
| Object | Shamash as god of justice |
—
|
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: Shamash as god of justice | Statement: [Ebabbar, deityRoleAtTemple, Shamash as god of justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deityRoleAtTemple Context triple: [Ebabbar, deityRoleAtTemple, Shamash as god of justice]
-
A.
roleAtTemple
chosen
Indicates that an entity holds or performs a specific role, function, or position at a particular temple.
-
B.
linkedTempleDeity
Indicates a relationship where a temple is associated with, or dedicated to, a particular deity.
-
C.
depictedDeity
Indicates that one entity is a deity who is shown or represented in an image, artwork, or visual depiction associated with another entity.
-
D.
servedDeity
Indicates that one entity acted in service, devotion, or worship toward a particular deity.
-
E.
portraysDeity
Indicates that one entity represents, depicts, or characterizes another entity as a deity or divine being.
- F. None of above.
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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61c90abc8190a9b9dc1f50db59fa |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:02 a.m.