Triple

T6343743
Position Surface form Disambiguated ID Type / Status
Subject Chemosh E142693 entity
Predicate hasCultCenter P1191 FINISHED
Object Kir-hareseth E68464 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: Kir-hareseth | Statement: [Chemosh, hasCultCenter, Kir-hareseth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kir-hareseth
Context triple: [Chemosh, hasCultCenter, Kir-hareseth]
  • A. Baal-hazor
    Baal-hazor is a location mentioned in the Hebrew Bible as the site where Absalom orchestrated the killing of his half-brother Amnon.
  • B. Saqar
    Saqar is a term in the Qur'an referring to a severe level of Hell associated with intense punishment for disbelievers.
  • C. Kāne-hekili
    Kāne-hekili is a Hawaiian deity aspect associated with thunder, often regarded as a powerful manifestation of the god Kāne in storm and weather phenomena.
  • D. Tirhuta
    Tirhuta is a historical Brahmic script traditionally used for writing the Maithili language in the Mithila region of India and Nepal.
  • E. Riblah chosen
    Riblah was an ancient town in Syria that served as a strategic military and administrative headquarters, notably used by the Babylonian king Nebuchadnezzar during the final conquest of Judah.
  • 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_69c008d5ab108190b346c465696824a9 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0674702d08190806ef0998960b797 completed March 22, 2026, 10:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6044051548190bd35bc17b72fab90 completed March 27, 2026, 4:14 a.m.
Created at: March 22, 2026, 4:31 p.m.