Triple

T4059110
Position Surface form Disambiguated ID Type / Status
Subject Jerash E84765 entity
Predicate hasAncientName P20952 FINISHED
Object Gerasa E355792 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: Gerasa | Statement: [Jerash, hasAncientName, Gerasa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gerasa
Context triple: [Jerash, hasAncientName, Gerasa]
  • A. Bethsaida
    Bethsaida was an ancient fishing village on the Sea of Galilee, traditionally known as the hometown of several of Jesus’s apostles in the New Testament.
  • B. Sepphoris
    Sepphoris was an important ancient Galilean city in Roman-era Palestine, known as a political and cultural center with a significant Jewish population and notable rabbinic activity.
  • C. Tabgha
    Tabgha is a lakeside area on the northwestern shore of the Sea of Galilee in Israel, traditionally revered as the site of the miracle of the multiplication of the loaves and fishes.
  • D. Madaba chosen
    Madaba is a historic Jordanian city renowned for its Byzantine and Umayyad-era mosaics, especially the famous 6th-century mosaic map of the Holy Land.
  • E. Heshbon
    Heshbon is an ancient city in the Transjordan region frequently mentioned in the Bible as a significant Moabite and later Israelite center.
  • 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_69aed933bec881909edfa28ebb69c634 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefbd13b4481908f9c09cc4f4a9724 completed March 9, 2026, 4:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69b562a6250081908f289f43b066b04d completed March 14, 2026, 1:29 p.m.
Created at: March 9, 2026, 3:38 p.m.