Triple

T9075261
Position Surface form Disambiguated ID Type / Status
Subject Inanna's Descent to the Underworld E217467 entity
Predicate mainCharacter P1183 FINISHED
Object Inanna E37687 NE 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: Inanna | Statement: [Inanna's Descent to the Underworld, mainCharacter, Inanna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Inanna
Context triple: [Inanna's Descent to the Underworld, mainCharacter, Inanna]
  • A. Inanna chosen
    Inanna is the ancient Mesopotamian goddess of love, beauty, sex, war, and political power, later known as Ishtar.
  • B. Ninhursag
    Ninhursag is a major Sumerian mother goddess associated with fertility, mountains, and the earth.
  • C. Ninlil
    Ninlil is a Mesopotamian goddess, traditionally known as the wife of the god Enlil and associated with air, grain, and the city of Nippur.
  • D. Astarte
    Astarte is an ancient Near Eastern goddess associated primarily with fertility, sexuality, and war, venerated across Canaanite, Phoenician, and later Mediterranean cultures.
  • E. Ninshubur
    Ninshubur is a Mesopotamian deity known primarily as the loyal sukkal (divine vizier and attendant) and messenger of the goddess Inanna.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca83d6c14c8190bc056d927f00a2a2 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc95c53274819099b3b3047bfe8cc8 completed April 1, 2026, 3:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1eaa8135081909225810ee5355bc3 completed April 5, 2026, 4:52 a.m.
Created at: March 30, 2026, 7:12 p.m.