Triple

T14766698
Position Surface form Disambiguated ID Type / Status
Subject Aretas IV Philopatris E347013 entity
Predicate successor P78 FINISHED
Object Malichus II E347014 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: Malichus II | Statement: [Aretas IV Philopatris, successor, Malichus II]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Malichus II
Context triple: [Aretas IV Philopatris, successor, Malichus II]
  • A. Malichus II chosen
    Malichus II was a 1st-century king of Nabatea who ruled from Petra and navigated his kingdom through the expanding influence of the Roman Empire.
  • B. Malichus I
    Malichus I was a 1st-century BCE Nabataean king who ruled from Petra and helped consolidate the power of the Nabataean kingdom in the Levant.
  • C. Basilisk II
    Basilisk II is an open-source emulator that allows modern computers to run classic 68k-based Apple Macintosh operating systems and software.
  • D. King Abrazza
    King Abrazza is a fictional monarch appearing as a character in the novel "Mardi" by Herman Melville.
  • E. Burnaburiash II
    Burnaburiash II was a prominent Kassite king of Babylon in the 14th century BCE, known for his extensive diplomatic correspondence with other major Near Eastern powers such as Egypt.
  • 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_69d822e8896c819091169882f9b20486 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec7f576c881909da70627f5897c94 completed April 14, 2026, 11:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe24b1ff0c81908d5dffbaf86c3ca3 completed May 8, 2026, 6 p.m.
Created at: April 10, 2026, 1:30 a.m.