Triple

T19137259
Position Surface form Disambiguated ID Type / Status
Subject Genesis 35 E468464 entity
Predicate alsoSetIn P54147 FINISHED
Object Ephrath 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: Ephrath | Statement: [Genesis 35, alsoSetIn, Ephrath]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ephrath
Context triple: [Genesis 35, alsoSetIn, Ephrath]
  • A. Ephrath chosen
    Ephrath is an ancient place mentioned in the Hebrew Bible, traditionally identified with Bethlehem in the land of Canaan.
  • B. Ephrata
    Ephrata is a small city in central Washington State that serves as the county seat of Grant County.
  • C. Anathoth
    Anathoth is an ancient Levitical town in the territory of Benjamin, mentioned in the Hebrew Bible and traditionally associated with the prophet Jeremiah.
  • D. Gibeah
    Gibeah was an ancient Israelite city in the territory of Benjamin, historically notable as the royal seat of King Saul.
  • E. Bethal
    Bethal is a small town in Mpumalanga, South Africa, known historically for its role in the region’s coal mining and agriculture.
  • 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.