Triple
T30168328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inanna and Enki |
E766852
|
entity |
| Predicate | portraysInannaAs |
P103298
|
FINISHED |
| Object | patron goddess of Uruk |
—
|
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: patron goddess of Uruk | Statement: [Inanna and Enki, portraysInannaAs, patron goddess of Uruk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysInannaAs Context triple: [Inanna and Enki, portraysInannaAs, patron goddess of Uruk]
-
A.
portraysPurushaAs
Indicates that one entity represents or depicts another entity as Purusha, the cosmic or primordial being.
-
B.
portraysDeity
chosen
Indicates that one entity represents, depicts, or characterizes another entity as a deity or divine being.
-
C.
portraysDraupadiAs
Indicates how an entity represents, depicts, or characterizes Draupadi in a particular manner or role.
-
D.
hasLoveAndFertilityGoddess
Indicates that an entity is associated with or possesses a goddess who embodies both love and fertility.
-
E.
depictedDeity
Indicates that one entity is a deity who is shown or represented in an image, artwork, or visual depiction associated with another entity.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 29, 2026, 7:23 p.m.