Triple
T9075197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eannatum |
E217465
|
entity |
| Predicate | predecessor |
P97
|
FINISHED |
| Object | Akurgal |
E648186
|
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: Akurgal | Statement: [Eannatum, predecessor, Akurgal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Akurgal Context triple: [Eannatum, predecessor, Akurgal]
-
A.
Akurgal
chosen
Akurgal is a Turkish surname most notably associated with the prominent archaeologist Ekrem Akurgal.
-
B.
Yasa'ur
Yasa'ur was a Mongol prince and military leader who played a significant role in the politics and conflicts of the Chagatai Khanate during the early 14th century.
-
C.
Boorga
Boorga is a small rural locality within the Hay Shire local government area in New South Wales, Australia.
-
D.
Orshuun Gol
Orshuun Gol is a river that serves as one of the main tributaries feeding Hulun Lake in northeastern Asia.
-
E.
Boghni
Boghni is a town and commune in northern Algeria’s Kabylie region, known for its Berber (Amazigh) cultural heritage and mountainous surroundings.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc95c4026c8190b553aedb9f4beabb |
completed | April 1, 2026, 3:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffdfe16c4819092c884bc3fe5daeb |
completed | April 3, 2026, 5:50 p.m. |
Created at: March 30, 2026, 7:12 p.m.