Triple

T4768910
Position Surface form Disambiguated ID Type / Status
Subject Tabernacle E105876 entity
Predicate associatedWithPerson P37 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: [Tabernacle, associatedWithPerson, Bezalel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bezalel
Context triple: [Tabernacle, associatedWithPerson, 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. Nadab
    Nadab is a biblical figure, the eldest son of Aaron who served as a priest during the Israelites’ wilderness period.
  • C. Hiram
    Hiram is a masculine given name of Hebrew origin, traditionally meaning "exalted brother" or "my brother is exalted."
  • D. Heman the Ezrahite
    Heman the Ezrahite is a biblical figure traditionally regarded as the wise author of Psalm 88 and noted for his exceptional wisdom in the Old Testament.
  • E. Salomo
    Salomo is the given name of Johann Salomo Semler, an influential 18th-century German theologian and pioneer of historical-critical biblical scholarship.
  • 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_69bd43f226fc8190b867cc249c2a9042 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6537eb80819096e0ae906c59d605 completed March 20, 2026, 3:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69be3a8f7318819088839becd09577ce completed March 21, 2026, 6:28 a.m.
Created at: March 20, 2026, 1:21 p.m.