Triple
T15758885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rim-Sin I |
E382040
|
entity |
| Predicate | relative |
P37
|
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: [Rim-Sin I, relative, Kudur-Mabuk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kudur-Mabuk Context triple: [Rim-Sin I, relative, 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b35ea48190a758ee76a57b5451 |
completed | April 16, 2026, 3 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff9096d65c81908755cae83cc48e61 |
completed | May 9, 2026, 7:52 p.m. |
Created at: April 10, 2026, 4:47 a.m.