Triple

T14095629
Position Surface form Disambiguated ID Type / Status
Subject Achaemenid satrapy of Babylonia E339246 entity
Predicate majorCity P316 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: [Achaemenid satrapy of Babylonia, majorCity, Nippur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nippur
Context triple: [Achaemenid satrapy of Babylonia, majorCity, 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. Eridu
    Eridu is an ancient Sumerian city often regarded as one of the world’s earliest urban centers and a significant religious and cultural hub in Mesopotamian civilization.
  • 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. Harapha
    Harapha is a boastful Philistine giant who serves as Samson’s arrogant antagonist in John Milton’s tragic closet drama "Samson Agonistes."
  • 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_69d81c69b5c8819094aa1abf18302908 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5fb7fb3c819083266dbe7e93aaff completed April 14, 2026, 3:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcf7de2af88190b9ed8cfeece74e50 completed May 7, 2026, 8:36 p.m.
Created at: April 9, 2026, 10:22 p.m.