Triple

T10433518
Position Surface form Disambiguated ID Type / Status
Subject Al-Doha E245977 entity
Predicate locatedNear P294 FINISHED
Object Beit Jala E51577 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: Beit Jala | Statement: [Al-Doha, locatedNear, Beit Jala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beit Jala
Context triple: [Al-Doha, locatedNear, Beit Jala]
  • A. Beit Jala chosen
    Beit Jala is a historic Palestinian town in the Bethlehem Governorate of the West Bank, known for its Christian heritage, olive groves, and scenic hillside location.
  • B. Beit Jann
    Beit Jann is a predominantly Druze village in northern Israel known for its high elevation, scenic views, and rich Druze cultural heritage.
  • C. Tulkarm
    Tulkarm is a Palestinian city in the northwestern West Bank, near the Green Line, known as an agricultural and commercial center with historical and political significance.
  • D. Isfiya
    Isfiya is a Druze-majority village and local council located on Mount Carmel in northern Israel.
  • E. al-Bireh
    al-Bireh is a Palestinian city in the central West Bank that forms a twin urban center with nearby Ramallah and serves as an important administrative and commercial hub.
  • 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_69d381bf3dc08190bf35a2643e4e8f22 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4ea65afe08190b91260c9267a0f14 completed April 7, 2026, 11:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69d87eb8c70481909b9320af15f2b5e9 completed April 10, 2026, 4:38 a.m.
Created at: April 6, 2026, 12:14 p.m.