Triple

T9489758
Position Surface form Disambiguated ID Type / Status
Subject Balaam’s oracles E228853 entity
Predicate mention P831 FINISHED
Object Asshur E40938 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: Asshur | Statement: [Balaam’s oracles, mention, Asshur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Asshur
Context triple: [Balaam’s oracles, mention, Asshur]
  • A. Ashur chosen
    Ashur is an ancient Mesopotamian city in northern Iraq that served as the first capital and religious center of the Assyrian Empire.
  • B. Dur-Sharrukin
    Dur-Sharrukin was the short-lived but grandiose capital city built by the Assyrian king Sargon II in the late 8th century BCE, notable for its monumental palaces and reliefs.
  • C. Hamath
    Hamath is an ancient city of Syria, frequently mentioned in Near Eastern and biblical sources, located at the site of modern Hama on the Orontes River.
  • D. Borsippa
    Borsippa was an important ancient Mesopotamian city near Babylon, known especially for its prominent temple and ziggurat dedicated to the god Nabu.
  • E. Sippar
    Sippar was an important ancient Mesopotamian city, renowned as a religious and administrative center particularly associated with the sun god Shamash.
  • 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_69ca847424f081908180305555139f7a completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd80c6f6bc8190aa09422508bd5d23 completed April 1, 2026, 8:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69d12d202b748190b78e4e972b1ce08d completed April 4, 2026, 3:24 p.m.
Created at: March 30, 2026, 7:55 p.m.