Triple

T16427720
Position Surface form Disambiguated ID Type / Status
Subject Northern Jordan E398986 entity
Predicate hasCity P316 FINISHED
Object Mafraq E423188 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: Mafraq | Statement: [Northern Jordan, hasCity, Mafraq]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mafraq
Context triple: [Northern Jordan, hasCity, Mafraq]
  • A. Mafraq chosen
    Mafraq is a city in northern Jordan that serves as a strategic transport hub and gateway to the Syrian border and surrounding desert regions.
  • B. Umm al-Ghanam
    Umm al-Ghanam is a village in northern Israel that forms part of the Arab local council of Shibli–Umm al-Ghanam near Mount Tabor.
  • C. Tafilah
    Tafilah is a town in southern Jordan known for its historical significance, agricultural surroundings, and location in the rugged highlands region.
  • D. Al-Bureij
    Al-Bureij is a Palestinian refugee camp and urban locality in the central Gaza Strip.
  • E. al-Qastal
    al-Qastal is a strategically located Palestinian village near Jerusalem that became a key battleground during the 1948 Arab–Israeli War.
  • 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_69d87f2b9024819085c20e52de95d583 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e328fc223c8190bbed29907351a6f6 completed April 18, 2026, 6:47 a.m.
NED1 Entity disambiguation (via context triple) batch_6a008a2363208190beb218e633d0627e completed May 10, 2026, 1:37 p.m.
Created at: April 10, 2026, 5:09 a.m.