Triple

T19137262
Position Surface form Disambiguated ID Type / Status
Subject Genesis 35 E468464 entity
Predicate alsoSetIn P54147 FINISHED
Object Mamre NE NERFINISHED

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: Mamre | Statement: [Genesis 35, alsoSetIn, Mamre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mamre
Context triple: [Genesis 35, alsoSetIn, Mamre]
  • A. Mamre chosen
    Mamre is an ancient site near Hebron in the biblical land of Canaan, traditionally associated with Abraham and significant events in the Hebrew Bible.
  • B. Mizpah
    Mizpah is an ancient biblical site in Gilead known as the place where Jacob and Laban formalized their covenant before parting ways.
  • C. Mizpah
    Mizpah was an ancient Israelite town in the central hill country that served as a significant religious, political, and military gathering place in the Hebrew Bible.
  • D. Eben-Ezer
    Eben-Ezer is a biblical place name mentioned in the Old Testament as the site of key battles between the Israelites and the Philistines.
  • E. Mesḥa
    Mesḥa is the former name of the modern Israeli town of Kfar Tavor, located in the Lower Galilee region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8dd0796a48190b34ce4cd9d3f3be5 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e3edd1c48190b86bef530ebbd092 completed April 20, 2026, 8:29 a.m.
Created at: April 10, 2026, 12:05 p.m.