Triple

T16466951
Position Surface form Disambiguated ID Type / Status
Subject King of Babylon E399957 entity
Predicate positionHeldBy P8 FINISHED
Object Kudur-Mabuk E1175161 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: Kudur-Mabuk | Statement: [King of Babylon, positionHeldBy, Kudur-Mabuk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kudur-Mabuk
Context triple: [King of Babylon, positionHeldBy, Kudur-Mabuk]
  • A. Kudur-Mabuk chosen
    Kudur-Mabuk was an Amorite ruler and influential political figure in ancient Mesopotamia, known for establishing a powerful dynasty in Larsa.
  • B. Tahmuras
    Tahmuras is a legendary king in Iranian mythology, famed in the Shahnameh for subduing demons and advancing civilization during the early mythical dynasties.
  • C. Malgobek
    Malgobek is a town in the North Caucasus region of Russia known for its oil industry and role in World War II.
  • 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. Samalkha
    Samalkha is a town in the northern Indian state of Haryana, known for its industrial activity and location along major transport routes.
  • 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_69d87f2dac988190b74d6e185fa88ba4 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32dcd707081908fb7ca91a8c09e0a completed April 18, 2026, 7:07 a.m.
NED1 Entity disambiguation (via context triple) batch_6a004f575ed48190a24d6af74565189d completed May 10, 2026, 9:26 a.m.
Created at: April 10, 2026, 5:11 a.m.