Triple

T15850108
Position Surface form Disambiguated ID Type / Status
Subject Nebo E384311 entity
Predicate hasNameOrigin P3325 FINISHED
Object deity Nabu E212321 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: deity Nabu | Statement: [Nebo, hasNameOrigin, deity Nabu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: deity Nabu
Context triple: [Nebo, hasNameOrigin, deity Nabu]
  • A. Nabu chosen
    Nabu is the Mesopotamian god of wisdom and writing, revered as the divine scribe and patron of scribes.
  • B. Nabu-balatsu-iqbi
    Nabu-balatsu-iqbi was a prominent Babylonian nobleman of the 6th century BCE, best known as the father of the Neo-Babylonian king Nabonidus.
  • C. Nabû-nāhid
    Nabû-nāhid was a Persian-appointed governor (satrap) of the Achaemenid province of Babylonia, overseeing the region’s administration under imperial rule.
  • D. Marduk
    Marduk is the chief god of Babylon in ancient Mesopotamian religion, associated with creation, kingship, and the defeat of the chaos monster Tiamat.
  • E. Amel-Marduk
    Amel-Marduk was a 6th-century BCE king of Babylon, known from biblical and cuneiform sources as the successor of Nebuchadnezzar II and for releasing the Judean king Jehoiachin from prison.
  • 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_69d86da422088190aac39e32e6c68429 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e14cab0fe48190bd6629e071761e91 completed April 16, 2026, 8:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa145f2dc819092db805806b6e1d5 completed May 9, 2026, 9:04 p.m.
Created at: April 10, 2026, 4:50 a.m.