Triple
T30179538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Ningirsu |
E767162
|
entity |
| Predicate | hasDeityRoleOfNingirsu |
P118406
|
FINISHED |
| Object | warrior god |
—
|
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: warrior god | Statement: [Temple of Ningirsu, hasDeityRoleOfNingirsu, warrior god]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeityRoleOfNingirsu Context triple: [Temple of Ningirsu, hasDeityRoleOfNingirsu, warrior god]
-
A.
hasSupremeDeityRole
Indicates that an entity holds the highest divine or ultimate god role within a religious or mythological hierarchy.
-
B.
roleOfReferencedDeity
chosen
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
C.
hasGuardianDeity
Indicates that an entity is under the protection or patronage of a specific guardian deity.
-
D.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
E.
hasDeityAspect
Indicates that one entity embodies, represents, or functions as a specific divine aspect or manifestation of another 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: April 29, 2026, 7:26 p.m.