Triple

T13450407
Position Surface form Disambiguated ID Type / Status
Subject King of Assyria E320593 entity
Predicate hasCapital P204 FINISHED
Object Dur-Sharrukin E210518 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: Dur-Sharrukin | Statement: [King of Assyria, hasCapital, Dur-Sharrukin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dur-Sharrukin
Context triple: [King of Assyria, hasCapital, Dur-Sharrukin]
  • A. Dur-Sharrukin chosen
    Dur-Sharrukin was the short-lived but grandiose capital city built by the Assyrian king Sargon II in the late 8th century BCE, notable for its monumental palaces and reliefs.
  • B. Sippar
    Sippar was an important ancient Mesopotamian city, renowned as a religious and administrative center particularly associated with the sun god Shamash.
  • C. Ashur
    Ashur is an ancient Mesopotamian city in northern Iraq that served as the first capital and religious center of the Assyrian Empire.
  • D. Ashur
    Ashur is the principal deity of the ancient Assyrian pantheon, associated with kingship, war, and the identity of the Assyrian state.
  • E. Shuruppak
    Shuruppak was an important ancient Sumerian city in southern Mesopotamia, traditionally associated with early urban development and the Sumerian flood myth.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaef973b08190a3d7fe1c2a913cff completed April 12, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7462340548190b156a8213f5e2556 completed May 3, 2026, 12:57 p.m.
Created at: April 9, 2026, 9:41 p.m.