Triple
T16558204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamech |
E402263
|
entity |
| Predicate | sonOf |
P25213
|
FINISHED |
| Object | Methuselah |
E146338
|
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: Methuselah | Statement: [Lamech, sonOf, Methuselah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Methuselah Context triple: [Lamech, sonOf, Methuselah]
-
A.
Methuselah
chosen
Methuselah is a biblical patriarch famed for his extraordinary longevity, traditionally said to have lived 969 years.
-
B.
Enoch
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.
-
C.
Enoch
Enoch is a small city in Iron County, Utah, known for its residential communities and proximity to Cedar City.
-
D.
Enosh
Enosh is a biblical figure recognized as a grandson of Adam and an early patriarch in the Book of Genesis.
-
E.
Ziusudra
Ziusudra is a figure from ancient Mesopotamian mythology, often regarded as a Sumerian flood hero who survives a great deluge and attains immortality, paralleling later characters like Utnapishtim and 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576bce0c819087ab36f7dec5c394 |
completed | April 18, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0067bcb698819092ede6ba4f8a4a2b |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:15 a.m.