Triple

T3698064
Position Surface form Disambiguated ID Type / Status
Subject Amorites E78505 entity
Predicate notableRuler P22 FINISHED
Object Hammurabi E135391 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: Hammurabi | Statement: [Amorites, notableRuler, Hammurabi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hammurabi
Context triple: [Amorites, notableRuler, Hammurabi]
  • A. Hammurabi chosen
    Hammurabi was the sixth king of Babylon, best known for creating one of the earliest and most influential written legal codes in ancient Mesopotamia.
  • B. Sargon of Akkad
    Sargon of Akkad was an ancient Mesopotamian king who founded the Akkadian Empire, often regarded as the world’s first great empire.
  • C. Hamura
    Hamura is a city in western Tokyo, Japan, known for its residential neighborhoods and proximity to the Tama River.
  • D. Shulgi of Ur
    Shulgi of Ur was a powerful king of the Third Dynasty of Ur in ancient Mesopotamia, renowned for his extensive administrative reforms, monumental building projects, and promotion of Sumerian culture and literature.
  • E. Naram-Sin of Akkad
    Naram-Sin of Akkad was a powerful Mesopotamian king of the Akkadian Empire, famed for declaring himself a god and expanding the empire to its greatest territorial extent.
  • 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_69ad85e3b1888190abc983e06968696d completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc512ba188190a15bcacafac3f476 completed March 8, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4c3dbb7fc81909df2e7a4755cce28 completed March 14, 2026, 2:11 a.m.
Created at: March 8, 2026, 3:26 p.m.