Triple
T15017138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shachar |
E377984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | figure in Hebrew tradition |
C5130
|
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: figure in Hebrew tradition Context triple: [Shachar, instanceOf, figure in Hebrew tradition]
-
A.
figure in Jewish tradition
chosen
A figure in Jewish tradition is an individual—historical, legendary, or symbolic—who plays a significant role in Jewish religious texts, narratives, law, or cultural memory.
-
B.
figure in Abrahamic religions
A figure in Abrahamic religions is an individual—divine, prophetic, angelic, or historical—who plays a significant role within the narratives, doctrines, or practices of Judaism, Christianity, and/or Islam.
-
C.
figure in Ethiopian tradition
A figure in Ethiopian tradition is a culturally significant personage—real, legendary, or symbolic—who embodies the values, beliefs, and historical memory of Ethiopian society through stories, rituals, and artistic representations.
-
D.
era in Jewish history
An era in Jewish history is a distinct period marked by characteristic religious, cultural, political, and social developments that shape the trajectory and identity of the Jewish people.
-
E.
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.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:55 a.m.