Triple
T12934798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goliath |
E309478
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in the Hebrew Bible |
C5606
|
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: character in the Hebrew Bible Context triple: [Goliath, instanceOf, character in the Hebrew Bible]
-
A.
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.
-
B.
artifact described in the Hebrew Bible
An artifact described in the Hebrew Bible is any physical object, tool, structure, or item mentioned within the biblical texts that holds religious, cultural, or historical significance in the narrative of ancient Israel.
-
C.
event in the Hebrew Bible
An event in the Hebrew Bible is a narrated occurrence—historical, theological, or symbolic—in which God’s purposes unfold through actions, experiences, or interventions in the lives of individuals or communities.
-
D.
location mentioned in the Hebrew Bible
A "location mentioned in the Hebrew Bible" is any geographically identifiable place—such as a city, region, landmark, or territory—explicitly referenced within the canonical texts of the Hebrew Scriptures.
-
E.
biblical character
chosen
A biblical character is an individual, either historical or symbolic, depicted in the Bible whose actions, experiences, and relationships contribute to the religious, moral, and narrative themes of the scriptural text.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:42 p.m.