Triple

T17222413
Position Surface form Disambiguated ID Type / Status
Subject Jordan Petroleum Refinery E418018 entity
Predicate locatedIn P40 FINISHED
Object Zarqa E88503 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: Zarqa | Statement: [Jordan Petroleum Refinery, locatedIn, Zarqa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zarqa
Context triple: [Jordan Petroleum Refinery, locatedIn, Zarqa]
  • A. Zarqa chosen
    Zarqa is a large industrial city in northeastern Jordan known for its factories, military presence, and role as a key economic hub.
  • B. Zahleh
    Zahleh is a major city in Lebanon’s Beqaa Valley, known for its predominantly Christian population, wineries, and role as a regional cultural and economic center.
  • C. Mafraq
    Mafraq is a city in northern Jordan that serves as a strategic transport hub and gateway to the Syrian border and surrounding desert regions.
  • D. El Zarqa
    El Zarqa is a town in Egypt situated along the Damietta branch of the Nile River.
  • 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_69d886d779488190b131369541c04e7d completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42ddf2c3c8190b6adceaaefd4ccbf completed April 19, 2026, 1:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a01793cfaf08190bff9a6efe01d5bea completed May 11, 2026, 6:37 a.m.
Created at: April 10, 2026, 5:38 a.m.