Triple
T3745092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parting of the Sea of Reeds |
E81191
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Exodus narrative episode |
C5094
|
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: Exodus narrative episode Context triple: [Parting of the Sea of Reeds, instanceOf, Exodus narrative episode]
-
A.
Exodus narrative element
chosen
An Exodus narrative element is a story component that depicts the journey from oppression or bondage toward liberation and covenantal identity, often marked by divine intervention, conflict with oppressive powers, and transformative passage through liminal spaces.
-
B.
Ten Commandments
The Ten Commandments are a foundational set of biblical moral laws, traditionally believed to be given by God to Moses, that outline core duties toward God and other people.
-
C.
New Testament event
A New Testament event is a significant occurrence or episode described in the New Testament writings that contributes to the narrative, theology, or historical context of early Christianity.
-
D.
Nasi of the Sanhedrin
The Nasi of the Sanhedrin was the president and highest-ranking official of the ancient Jewish high court, responsible for leading its deliberations, representing the Jewish people to external authorities, and guiding religious and legal policy.
-
E.
mythological event
A mythological event is a significant occurrence within a culture’s traditional stories or legends, often involving gods, heroes, or supernatural forces that explain natural phenomena, origins, or moral truths.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:35 p.m.