Triple
T14683353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berosus |
E344843
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Babylonian priest |
C28433
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Babylonian priest Context triple: [Berosus, instanceOf, Babylonian priest]
-
A.
Babylonian scholar
chosen
A Babylonian scholar is an educated individual in ancient Mesopotamia who studies, preserves, and interprets knowledge in fields such as astronomy, mathematics, divination, and literature, often serving in temples or royal courts.
-
B.
Babylonian Jew
A Babylonian Jew is a member of the Jewish community historically rooted in Babylonia (primarily in present-day Iraq), whose religious, cultural, and intellectual life was shaped by centuries of diaspora experience and the development of major Jewish texts such as the Babylonian Talmud.
-
C.
Neo-Babylonian prince
A Neo-Babylonian prince is a royal male heir or close relative of the king in the Neo-Babylonian Empire (c. 626–539 BCE), raised within the courtly, military, and religious traditions that prepared him for governance and dynastic continuity.
-
D.
Neo-Babylonian king
A Neo-Babylonian king is the sovereign ruler of the Neo-Babylonian Empire (c. 626–539 BCE), responsible for military leadership, monumental building projects, religious patronage, and the administration of law and tribute across Mesopotamia.
-
E.
Babylonian god
A Babylonian god is a divine being from ancient Mesopotamian religion, associated with specific cosmic functions, cities, or aspects of life, and worshiped through rituals, temples, and myths.
- F. None of above.
Provenance (1 batch)
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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:28 a.m.