Triple
T32530994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moses at the burning bush |
E831451
|
entity |
| Predicate | MosesFamilyConnection |
P175000
|
FINISHED |
| Object | Jethro his father-in-law |
—
|
NE NERFINISHED |
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: Jethro his father-in-law | Statement: [Moses at the burning bush, MosesFamilyConnection, Jethro his father-in-law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MosesFamilyConnection Context triple: [Moses at the burning bush, MosesFamilyConnection, Jethro his father-in-law]
-
A.
MosesResponse
Indicates how Moses reacts, replies, or responds in a given situation or interaction.
-
B.
relationshipToMosesPray
Indicates that one entity engages in an act of prayer directed toward or on behalf of Moses.
-
C.
offeredByMoses
Indicates that something (such as a law, commandment, or offering) is presented, given, or instituted by Moses.
-
D.
viewsMosesAs
Indicates that one entity regards or considers another entity in the role, status, or identity of Moses.
-
E.
hasNotableRabbinicFamily
Indicates that an individual belongs to or descends from a family recognized for its prominence or distinction in rabbinic leadership or scholarship.
- F. None of above. chosen
Provenance (4 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 1:01 a.m.