Triple
T14630112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis 36 |
E343458
|
entity |
| Predicate | mentions |
P831
|
FINISHED |
| Object | Zerah |
E602605
|
NE 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: Zerah | Statement: [Genesis 36, mentions, Zerah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zerah Context triple: [Genesis 36, mentions, Zerah]
-
A.
Zerah
Zerah is a minor biblical figure mentioned in the Book of Genesis as one of the sons of Judah and Tamar.
-
B.
Zerah
chosen
Zerah is a minor biblical figure mentioned in genealogical records as a descendant within the tribe of Zebulun.
-
C.
Zethus
Zethus is a figure in Greek mythology, a son of Zeus and Antiope and twin brother of Amphion, known as a co-founder and ruler of the city of Thebes.
-
D.
Reuel
Reuel is a biblical figure identified as another name for Jethro, the Midianite priest and father-in-law of Moses.
-
E.
Reuel
Reuel is the middle name of famed English author and philologist J. R. R. Tolkien, used as part of his full name John Ronald Reuel Tolkien.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4a912248190a3df7f821395c776 |
completed | April 14, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdd5d0514081908c2bdc4fb77b1a7a |
completed | May 8, 2026, 12:23 p.m. |
Created at: April 10, 2026, 1:26 a.m.