Triple

T2102103
Position Surface form Disambiguated ID Type / Status
Subject Enlil E37112 entity
Predicate mainCultCenter P8490 FINISHED
Object Nippur E38027 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: Nippur | Statement: [Enlil, mainCultCenter, Nippur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nippur
Context triple: [Enlil, mainCultCenter, Nippur]
  • A. Nippur chosen
    Nippur was an ancient Sumerian city in Mesopotamia that served as a major religious center dedicated to the god Enlil.
  • B. Sippar
    Sippar was an important ancient Mesopotamian city, renowned as a religious and administrative center particularly associated with the sun god Shamash.
  • C. Lagash
    Lagash was an important ancient Sumerian city-state in southern Mesopotamia, known for its early political power, distinctive art, and extensive cuneiform records.
  • D. 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.
  • E. Ur of the Chaldeans
    Ur of the Chaldeans is an ancient Mesopotamian city traditionally regarded as the birthplace of the biblical patriarch Abraham.
  • 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_69a8861828948190924aa30c08806b3a completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abbabc83a8819091f786f21d33b5a6 completed March 7, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae518fb0b4819096a8ce455e22661a completed March 9, 2026, 4:50 a.m.
Created at: March 4, 2026, 7:43 p.m.