Triple
T30106567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-hulhul |
E765148
|
entity |
| Predicate | equivalentDeityName |
P141581
|
FINISHED |
| Object | Sin |
—
|
NE NERFINISHED |
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: Sin | Statement: [E-hulhul, equivalentDeityName, Sin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentDeityName Context triple: [E-hulhul, equivalentDeityName, Sin]
-
A.
equivalentMythologicalName
chosen
Indicates that two entities share the same identity in mythology, representing different names or versions of the same mythological figure.
-
B.
comparableDeity
Indicates that one deity is considered comparable to another in terms of role, attributes, status, or function.
-
C.
equivalentInGreekReligion
Indicates that two religious figures, concepts, or practices are counterparts or direct analogues of each other within the context of Greek religion.
-
D.
equivalentInRomanMythology
Indicates that one entity corresponds to or is identified as the Roman-mythology counterpart of another entity from a different mythological tradition.
-
E.
veneratedDeityNameVariant
Indicates that the referenced name is an alternative or variant form used to venerate or refer to a particular deity.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 7:09 p.m.