Triple
T25073880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hosea 2:23 |
E627995
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | verse in the Book of Hosea |
C33351
|
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: verse in the Book of Hosea Context triple: [Hosea 2:23, instanceOf, verse in the Book of Hosea]
-
A.
verse in the Book of Exodus
A verse in the Book of Exodus is a discrete, numbered textual unit that conveys a specific event, command, dialogue, or narrative detail within the broader account of Israel’s deliverance from Egypt and covenant formation with God.
-
B.
verse in the Book of Deuteronomy
A verse in the Book of Deuteronomy is a discrete, numbered textual unit within this biblical book that conveys a specific command, teaching, narrative detail, or theological statement within Moses’ final speeches to Israel.
-
C.
verse of the Hebrew Bible
chosen
A verse of the Hebrew Bible is a discrete, traditionally numbered textual unit that forms part of the canonical Hebrew Scriptures, often conveying a complete thought, law, narrative detail, or poetic line.
-
D.
character in the Book of Genesis
A character in the Book of Genesis is an individual—divine, human, or other—who participates in the foundational narratives of creation, covenant, ancestry, and early human history as recorded in the first book of the Hebrew Bible.
-
E.
Sumerian temple hymn
A Sumerian temple hymn is an ancient Mesopotamian poetic composition that praises a specific temple and its deity, celebrating the sacred space’s divine presence, power, and ritual significance.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:20 a.m.