Triple

T8895625
Position Surface form Disambiguated ID Type / Status
Subject Eanna temple complex E211798 entity
Predicate locatedIn P40 FINISHED
Object Uruk E37108 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: Uruk | Statement: [Eanna temple complex, locatedIn, Uruk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Uruk
Context triple: [Eanna temple complex, locatedIn, Uruk]
  • A. Uruk chosen
    Uruk was one of the earliest major cities in ancient Sumer and Mesopotamia, renowned as a political, religious, and cultural center often associated with the legendary king Gilgamesh.
  • B. Shumerlya
    Shumerlya is a town in the Chuvash Republic of Russia, known as a local industrial and transport center.
  • C. Esagila
    Esagila was the principal temple complex dedicated to the god Marduk in ancient Babylon, serving as a major religious and ceremonial center of Mesopotamia.
  • D. Lagash
    Lagash was an important ancient Sumerian city-state in southern Mesopotamia, known for its early political power, distinctive art, and extensive cuneiform records.
  • E. Larsa
    Larsa was an important ancient Sumerian city-state in southern Mesopotamia, known for its political power and temple-centered religious life during the early second millennium BCE.
  • 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_69ca83918d3081909b326fa3750cb8c8 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc61be2c2081908f39cccdc149872d completed April 1, 2026, 12:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfac02974881908a7e8d9cfa47e624 completed April 3, 2026, 12:01 p.m.
Created at: March 30, 2026, 6:54 p.m.