Triple
T10720470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanoch |
E252804
|
entity |
| Predicate | isDistinctFrom |
P1612
|
FINISHED |
| Object | Enoch son of Cain |
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 son of Cain | Statement: [Hanoch, isDistinctFrom, Enoch son of Cain]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Enoch son of Cain Context triple: [Hanoch, isDistinctFrom, Enoch son of Cain]
-
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.
Caín
Caín is a small mountain village in the Picos de Europa in northern Spain, known as a popular gateway for hikers and climbers exploring the surrounding peaks and gorges.
-
C.
Cain
Cain is a biblical figure known as the firstborn son of Adam and Eve and for committing the first murder by killing his brother Abel.
-
D.
Enosh
Enosh is a biblical figure recognized as a grandson of Adam and an early patriarch in the Book of Genesis.
-
E.
Lamech
Lamech is a biblical patriarch mentioned in the Book of Genesis as part of the antediluvian genealogy leading to Noah.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70d42033c81908cafe500213a9da1 |
completed | April 9, 2026, 2:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dbb72b9ce08190a9134f3365d3f8cb |
completed | April 12, 2026, 3:15 p.m. |
Created at: April 8, 2026, 9:13 p.m.