Triple
T30250233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moses and Pharaoh |
E769177
|
entity |
| Predicate | narrativeRoleOfMoses |
P148046
|
FINISHED |
| Object | leader of the Israelites |
—
|
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: leader of the Israelites | Statement: [Moses and Pharaoh, narrativeRoleOfMoses, leader of the Israelites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeRoleOfMoses Context triple: [Moses and Pharaoh, narrativeRoleOfMoses, leader of the Israelites]
-
A.
viewsMosesAs
Indicates that one entity regards or considers another entity in the role, status, or identity of Moses.
-
B.
MosesResponse
Indicates how Moses reacts, replies, or responds in a given situation or interaction.
-
C.
roleInExodusTradition
Indicates having a specific function, status, or significance within the narratives, practices, or interpretations associated with the Exodus tradition.
-
D.
roleInExodus
chosen
Indicates that an entity has a specific role or function within the context of the Exodus event or narrative.
-
E.
MosesObjection
Indicates that Moses raises an objection, protest, or resistance in response to a command, request, or situation.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 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 29, 2026, 7:40 p.m.