Triple
T30705480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enki and Ninmah |
E781739
|
entity |
| Predicate | deityRoleOfEnki |
P9987
|
FINISHED |
| Object | god of wisdom |
—
|
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: god of wisdom | Statement: [Enki and Ninmah, deityRoleOfEnki, god of wisdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deityRoleOfEnki Context triple: [Enki and Ninmah, deityRoleOfEnki, god of wisdom]
-
A.
roleOfReferencedDeity
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
B.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
C.
deityCategory
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
D.
guardianDeitiesOrFigures
Indicates a protective or watchful relationship in which certain deities or figures serve as guardians over specific people, places, objects, or domains.
-
E.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c19e9688190907e555dc9973ba0 |
completed | May 2, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:35 p.m.