Triple

T21400113
Position Surface form Disambiguated ID Type / Status
Subject Beinn Narnain E527888 entity
Predicate usualAscentFrom P37604 FINISHED
Object Succoth 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: Succoth | Statement: [Beinn Narnain, usualAscentFrom, Succoth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Succoth
Context triple: [Beinn Narnain, usualAscentFrom, Succoth]
  • A. Succoth chosen
    Succoth is an ancient biblical town east of the Jordan River, mentioned in the Hebrew Bible in connection with the stories of Jacob and Gideon.
  • B. Mesḥa
    Mesḥa is the former name of the modern Israeli town of Kfar Tavor, located in the Lower Galilee region.
  • C. Ashkelon
    Ashkelon is an ancient coastal city in the southern Levant, historically significant as one of the principal cities of the Philistines.
  • D. Nitzana
    Nitzana is an ancient desert settlement in the Negev region of southern Israel, known for its archaeological remains and historical role on trade and pilgrimage routes.
  • E. Beersheba
    Beersheba is a major city in southern Israel, often regarded as the "Capital of the Negev" and known for its historical significance and rapid modern development.
  • 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_69e0b520ee3c8190abddbee7e37e834c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69ee62cf3e808190847ad66d2e65f9f2 completed April 26, 2026, 7:09 p.m.
Created at: April 16, 2026, 5:14 p.m.