Triple
T19141746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadab |
E468575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Israelite person |
C14175
|
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: ancient Israelite person Context triple: [Nadab, instanceOf, ancient Israelite person]
-
A.
Ancient Israelite
chosen
An Ancient Israelite is a member of the historical people and culture of Israel in the ancient Near East, characterized by a shared ethnic identity, language (Hebrew), religious traditions centered on Yahweh, and social life organized around tribes and later monarchies.
-
B.
Israelite
An Israelite is a member of the ancient Hebrew people, traditionally descended from the patriarch Jacob (also called Israel), who formed the tribes of Israel and developed the religious and cultural foundations of Judaism.
-
C.
Sumerian person
A Sumerian person is an individual belonging to the ancient Sumerian civilization of southern Mesopotamia, characterized by their participation in early urban society, cuneiform literacy, polytheistic religion, and agrarian-based economy.
-
D.
ancient Egyptian person
An ancient Egyptian person is an individual who lived in the Nile Valley civilization of ancient Egypt, shaped by its social hierarchy, religious beliefs, agricultural economy, and distinctive cultural practices.
-
E.
biblical character
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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:05 p.m.