Triple

T1151837
Position Surface form Disambiguated ID Type / Status
Subject Babylon E23692 entity
Predicate hasLanguage P15 FINISHED
Object Akkadian E37900 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: Akkadian | Statement: [Babylon, hasLanguage, Akkadian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Akkadian
Context triple: [Babylon, hasLanguage, Akkadian]
  • A. Akkadian chosen
    Akkadian is an extinct Semitic language of ancient Mesopotamia, historically used in Assyria and Babylonia and written in cuneiform script.
  • B. Akkad
    Akkad was an ancient Mesopotamian city and region best known as the center of the Akkadian Empire, one of the world’s earliest great empires.
  • C. Akkadians
    The Akkadians were an ancient Semitic-speaking people of Mesopotamia who established one of the world’s first empires under rulers like Sargon of Akkad.
  • D. Aramaic
    Aramaic is an ancient Semitic language historically spoken in the Near East, notable as a lingua franca of empires and as the everyday language of parts of the biblical and early Christian world.
  • E. Elamite
    Elamite is an ancient language of southwestern Iran, historically used in the kingdom of Elam and later as an administrative language under the Achaemenid Empire.
  • 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_69a493f0d32c8190ac74bad3c87f2641 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4bc744e7c81908f8612f2aad28600 completed March 1, 2026, 10:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac5eb5d36c8190916a43a5f41df144 completed March 7, 2026, 5:21 p.m.
Created at: March 1, 2026, 7:44 p.m.