Triple
T3718758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1 Enoch |
E81590
|
entity |
| Predicate | attributedTo |
P806
|
FINISHED |
| Object | Enoch |
E85967
|
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: Enoch | Statement: [1 Enoch, attributedTo, Enoch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Enoch Context triple: [1 Enoch, attributedTo, Enoch]
-
A.
Enoch
chosen
Enoch is a biblical and Qur’anic prophet revered for his exceptional piety and, in many traditions, for being taken up by God without experiencing death.
-
B.
Enosh
Enosh is a biblical figure recognized as a grandson of Adam and an early patriarch in the Book of Genesis.
-
C.
Bethuel
Bethuel is a biblical figure from the Book of Genesis, known as the father of Laban and Rebekah and a descendant of Abraham’s family line.
-
D.
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.
-
E.
Reuel
Reuel is a biblical figure identified as another name for Jethro, the Midianite priest and father-in-law of Moses.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca984844819087a2f6b20d2f19e7 |
completed | March 8, 2026, 7:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4ce1560bc81908fe936c426795f06 |
completed | March 14, 2026, 2:55 a.m. |
Created at: March 8, 2026, 3:34 p.m.