Triple

T15802545
Position Surface form Disambiguated ID Type / Status
Subject Aram-Damascus kingdom E383130 entity
Predicate ruler P403 FINISHED
Object Hazael E542950 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: Hazael | Statement: [Aram-Damascus kingdom, ruler, Hazael]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hazael
Context triple: [Aram-Damascus kingdom, ruler, Hazael]
  • A. Hazael of Aram-Damascus chosen
    Hazael of Aram-Damascus was a powerful 9th-century BCE king of Aram (Syria) known from biblical and Assyrian sources for his aggressive military campaigns against Israel and neighboring kingdoms.
  • B. Shallum
    Shallum is a biblical figure mentioned in the Hebrew Bible as the husband of the prophetess Huldah during the reign of King Josiah of Judah.
  • C. Shammah
    Shammah is a lesser-known son of Jesse mentioned in the Bible, traditionally recognized as one of King David’s older brothers.
  • D. Shammah
    Shammah is a minor biblical figure listed among the descendants of Esau in the Book of Genesis.
  • E. Eglon
    Eglon is a Moabite king from the Hebrew Bible, known for being assassinated by the Israelite judge Ehud in the Book of Judges.
  • 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_69d86da16e188190b89af699f1ed0bfe completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0b523bf508190af4a54bdc983a9a1 completed April 16, 2026, 10:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff90b2fd148190b3819d7c41505d52 completed May 9, 2026, 7:53 p.m.
Created at: April 10, 2026, 4:48 a.m.