Triple
T15853352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exodus 37 |
E384394
|
entity |
| Predicate | mentionsPerson |
P831
|
FINISHED |
| Object | Bezalel |
E219038
|
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: Bezalel | Statement: [Exodus 37, mentionsPerson, Bezalel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bezalel Context triple: [Exodus 37, mentionsPerson, Bezalel]
-
A.
Bezalel
chosen
Bezalel is a biblical artisan from the Book of Exodus, renowned as the chief craftsman chosen by God to design and construct the Tabernacle and its sacred furnishings.
-
B.
Oholiab
Oholiab is a biblical craftsman from the Book of Exodus who, alongside Bezalel, was divinely appointed to help design and construct the Tabernacle and its sacred furnishings.
-
C.
Nadab
Nadab was a king of the northern Kingdom of Israel in the Hebrew Bible, known as the son and short-reigning royal heir of Jeroboam I.
-
D.
Nadab
Nadab is a biblical figure, the eldest son of Aaron who served as a priest during the Israelites’ wilderness period.
-
E.
Hiram
Hiram is a masculine given name of Hebrew origin, traditionally meaning "exalted brother" or "my brother is exalted."
- 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_69e14cae96648190884a85f68b6e9fe1 |
completed | April 16, 2026, 8:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa941a0a481909c8d8e98861b46d6 |
completed | May 9, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.