Triple

T11501111
Position Surface form Disambiguated ID Type / Status
Subject LLBG E272664 entity
Predicate nearLocality P350 FINISHED
Object Ramla E64142 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: Ramla | Statement: [LLBG, nearLocality, Ramla]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ramla
Context triple: [LLBG, nearLocality, Ramla]
  • A. Ramla chosen
    Ramla is an Israeli city historically significant as a major religious and communal center for Karaite Jews.
  • B. Qalqilya
    Qalqilya is a Palestinian city in the northwestern West Bank, known for being almost completely encircled by the Israeli West Bank barrier.
  • C. 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.
  • D. Ashdod
    Ashdod is a major coastal city in southern Israel that serves as an important cultural and religious hub, including for the Karaite Jewish community.
  • E. Ma’an
    Ma’an is a major city in southern Jordan that serves as an important regional hub and gateway to nearby desert and archaeological sites.
  • 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_69d6aae2c3748190bed2ea50dfb160dc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85de3e9c881909d6c55334f7a832d completed April 10, 2026, 2:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69f165f5b3d081909c00144eb9291ff5 completed April 29, 2026, 1:59 a.m.
Created at: April 8, 2026, 9:36 p.m.