Triple
T30165099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anu district |
E766771
|
entity |
| Predicate | centralDeityRole |
P7648
|
FINISHED |
| Object | worship of the sky god Anu |
—
|
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: worship of the sky god Anu | Statement: [Anu district, centralDeityRole, worship of the sky god Anu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralDeityRole Context triple: [Anu district, centralDeityRole, worship of the sky god Anu]
-
A.
centralDeitySymbol
Indicates that one entity serves as the primary or central symbolic representation of a deity for another entity.
-
B.
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.
-
C.
mainDeity
chosen
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
D.
hasSupremeDeityRole
Indicates that an entity holds the highest divine or ultimate god role within a religious or mythological hierarchy.
-
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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 29, 2026, 7:23 p.m.