Triple
T14630122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis 36 |
E343458
|
entity |
| Predicate | mentions |
P831
|
FINISHED |
| Object | Ezer |
E905939
|
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: Ezer | Statement: [Genesis 36, mentions, Ezer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ezer Context triple: [Genesis 36, mentions, Ezer]
-
A.
Ezer
chosen
Ezer is a Hebrew given name most notably borne by Ezer Weizman, the seventh President of Israel and a former commander of the Israeli Air Force.
-
B.
Erezée
Erezée is a small rural municipality in the Ardennes region of southern Belgium, known for its scenic landscapes and quiet village character.
-
C.
Eza’r
Eza’r is the endonym used by the Chichimeca Jonaz people for their own indigenous community and language in Mexico.
-
D.
Zerah
Zerah is a minor biblical figure mentioned in the Book of Genesis as one of the sons of Judah and Tamar.
-
E.
Zerah
Zerah is a minor biblical figure mentioned in genealogical records as a descendant within the tribe of Zebulun.
- 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_69fda92ded848190b031d3ff29e54a00 |
completed | May 8, 2026, 9:13 a.m. |
Created at: April 10, 2026, 1:26 a.m.