Triple
T14630097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis 36 |
E343458
|
entity |
| Predicate | mentions |
P831
|
FINISHED |
| Object | Seir the Horite |
E1109482
|
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: Seir the Horite | Statement: [Genesis 36, mentions, Seir the Horite]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seir the Horite Context triple: [Genesis 36, mentions, Seir the Horite]
-
A.
Seir
chosen
Seir is a mountainous region in Edom, traditionally associated with the Horites and later the descendants of Esau in the Hebrew Bible.
-
B.
Auri-El
Auri-El is a chief elven deity in The Elder Scrolls universe, revered as the god of time and the progenitor of the Aldmeri peoples.
-
C.
Hedareb
Hedareb are a traditionally semi-nomadic Cushitic-speaking ethnic group primarily inhabiting northwestern Eritrea and parts of eastern Sudan.
-
D.
Setesh
Setesh is an alternative transliteration of Set, the ancient Egyptian god associated with chaos, storms, deserts, and disorder.
-
E.
Hadad
Hadad is a biblical figure traditionally regarded as one of the sons of Ishmael and an eponymous ancestor of an Ishmaelite clan.
- 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_69fde16e85488190b0dcc2ccd2f5df4d |
completed | May 8, 2026, 1:13 p.m. |
Created at: April 10, 2026, 1:26 a.m.