Triple
T12208841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exodus 18 |
E290902
|
entity |
| Predicate | characterRoleOfZipporah |
P27433
|
FINISHED |
| Object | wife of Moses |
—
|
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: wife of Moses | Statement: [Exodus 18, characterRoleOfZipporah, wife of Moses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterRoleOfZipporah Context triple: [Exodus 18, characterRoleOfZipporah, wife of Moses]
-
A.
biblicalFigureRole
chosen
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
B.
roleInWZRD
Indicates that an entity holds a specific role or function within the context of WZRD.
-
C.
narrativeRoleInSeries
Indicates the specific narrative function or role an entity plays within a particular series or serialized work.
-
D.
associatedBiblicalFigure
Indicates that one entity is linked or connected to a particular biblical figure, such as by reference, attribution, or traditional association.
-
E.
speakerRole
Indicates the functional role or capacity in which an entity is acting as a speaker within a communicative event.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.