Triple

T15724705
Position Surface form Disambiguated ID Type / Status
Subject Neo-Babylonian architecture E381188 entity
Predicate majorCenter P164 FINISHED
Object Borsippa E481292 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: Borsippa | Statement: [Neo-Babylonian architecture, majorCenter, Borsippa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Borsippa
Context triple: [Neo-Babylonian architecture, majorCenter, Borsippa]
  • A. Borsippa chosen
    Borsippa was an important ancient Mesopotamian city near Babylon, known especially for its prominent temple and ziggurat dedicated to the god Nabu.
  • B. Sippar
    Sippar was an important ancient Mesopotamian city, renowned as a religious and administrative center particularly associated with the sun god Shamash.
  • C. Shuruppak
    Shuruppak was an important ancient Sumerian city in southern Mesopotamia, traditionally associated with early urban development and the Sumerian flood myth.
  • D. 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.
  • E. Nippur
    Nippur was an ancient Sumerian city in Mesopotamia that served as a major religious center dedicated to the god Enlil.
  • 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_69d86d9cdb648190bf3171be0bd7d872 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e04fb1fdd4819088f3e243263e5f73 completed April 16, 2026, 2:55 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff9092e25c81909f86a580e78ff7ca completed May 9, 2026, 7:52 p.m.
Created at: April 10, 2026, 4:46 a.m.