Triple
T30170054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tashmetu |
E766894
|
entity |
| Predicate | divineHierarchy |
P9989
|
FINISHED |
| Object | member of the great gods of Babylonia |
—
|
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: member of the great gods of Babylonia | Statement: [Tashmetu, divineHierarchy, member of the great gods of Babylonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divineHierarchy Context triple: [Tashmetu, divineHierarchy, member of the great gods of Babylonia]
-
A.
divineLineage
Indicates that one entity is descended from, or originates from, a divine or god-like being.
-
B.
angelicHierarchy
Indicates a hierarchical relationship in which one angelic being holds a higher or lower rank or order relative to another within a structured celestial order.
-
C.
divineSign
Indicates that one entity serves as a supernatural or sacred omen, message, or signal from a divine source to another entity.
-
D.
divineStatus
Indicates that an entity possesses a sacred, godlike, or religiously exalted status in relation to another entity or within a given belief system.
-
E.
typeOfDeity
chosen
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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f0b25908190baf7f9dfef6ec6ce |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:24 p.m.