Triple
T9422070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juba I |
E227176
|
entity |
| Predicate | predecessor |
P97
|
FINISHED |
| Object | Hiempsal II |
E798690
|
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: Hiempsal II | Statement: [Juba I, predecessor, Hiempsal II]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hiempsal II Context triple: [Juba I, predecessor, Hiempsal II]
-
A.
Hiempsal II
chosen
Hiempsal II was a king of Numidia in the 1st century BC who ruled amid Roman civil conflicts and shifting alliances in North Africa.
-
B.
Hiempsal I
Hiempsal I was a 2nd-century BCE king of Numidia whose murder helped trigger the Jugurthine War against Rome.
-
C.
Huram
Huram is an alternative biblical form of the name Hiram, commonly associated with figures linked to the construction of Solomon’s Temple.
-
D.
Juhurim
Juhurim are a Jewish ethnic group from the eastern and northern Caucasus, particularly Dagestan and Azerbaijan, with their own distinct language (Juhuri) and cultural traditions.
-
E.
Huraymila
Huraymila is a small town in central Saudi Arabia known for its traditional character and location within the greater Riyadh region.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd6c2651c48190808281779fab49df |
completed | April 1, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d12233f89c8190979d76aee65c0d56 |
completed | April 4, 2026, 2:37 p.m. |
Created at: March 30, 2026, 7:48 p.m.