Triple
T30617829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exodus 27 |
E779360
|
entity |
| Predicate | sectionOfExodus |
P37110
|
FINISHED |
| Object | tabernacle instructions |
—
|
LITERAL 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: tabernacle instructions | Statement: [Exodus 27, sectionOfExodus, tabernacle instructions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionOfExodus Context triple: [Exodus 27, sectionOfExodus, tabernacle instructions]
-
A.
scripturalSection
chosen
Indicates a relationship where one text or passage is a specific section or subdivision within a larger scriptural work.
-
B.
roleInExodusTradition
Indicates having a specific function, status, or significance within the narratives, practices, or interpretations associated with the Exodus tradition.
-
C.
subsectionOfTanakh
Indicates that one text division is a recognized subsection within the larger structure of the Tanakh.
-
D.
roleInExodus
Indicates that an entity has a specific role or function within the context of the Exodus event or narrative.
-
E.
sectionOfHallel
Indicates that something is a specific section or part within the liturgical unit known as Hallel.
- F. None of above.
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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689eca0348190a4f8e54e0a56f797 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:26 p.m.