Triple
T29683851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exodus 24 |
E751030
|
entity |
| Predicate | describesTheophany |
P97695
|
FINISHED |
| Object | appearance of the God of Israel |
—
|
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: appearance of the God of Israel | Statement: [Exodus 24, describesTheophany, appearance of the God of Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesTheophany Context triple: [Exodus 24, describesTheophany, appearance of the God of Israel]
-
A.
miracleDescription
Indicates that a miraculous event or phenomenon is being described or characterized.
-
B.
occasionOfRevelation
Indicates the specific event, situation, or context during which a revelation or disclosure took place.
-
C.
scripturalDescription
chosen
Indicates that one entity provides a description, account, or characterization of another as found in or based on scriptural or sacred texts.
-
D.
describedThrough
Indicates that something is explained, represented, or conveyed by means of a particular medium, method, or description.
-
E.
meaningOfComponent:phaino
Indicates that the specified component conveys or expresses the meaning or sense of the term “phaino.”
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 28, 2026, 7:12 p.m.