Triple
T15703247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amorite dynasty of Larsa |
E380644
|
entity |
| Predicate | notableRuler |
P22
|
FINISHED |
| Object | Abisare |
E789029
|
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: Abisare | Statement: [Amorite dynasty of Larsa, notableRuler, Abisare]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abisare Context triple: [Amorite dynasty of Larsa, notableRuler, Abisare]
-
A.
Abisare
chosen
Abisare was an early 2nd-millennium BCE king of the ancient Mesopotamian city-state of Larsa, known for consolidating its power in southern Babylonia.
-
B.
Abas
Abas is a figure in Greek mythology known primarily as the son of Hypermnestra and a king of Argos in some traditions.
-
C.
Rasalhague
Rasalhague is the brightest star in the constellation Ophiuchus, representing the head of the serpent-bearer in the night sky.
-
D.
Argobba
Argobba is an endangered South Semitic language spoken by the Argobba people in central Ethiopia.
-
E.
Zababa
Zababa is an ancient Mesopotamian war god particularly venerated in the city of Kish.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f6e965881909319f85c51c6fb74 |
completed | April 16, 2026, 2:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff7577a3348190912fad48f7d8599e |
completed | May 9, 2026, 5:57 p.m. |
Created at: April 10, 2026, 4:45 a.m.