Triple

T20524829
Position Surface form Disambiguated ID Type / Status
Subject Ministry of Defense of Yemen E503906 entity
Predicate uses P98 FINISHED
Object Yemeni rial NE NERFINISHED

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: Yemeni rial | Statement: [Ministry of Defense of Yemen, uses, Yemeni rial]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yemeni rial
Context triple: [Ministry of Defense of Yemen, uses, Yemeni rial]
  • A. Yemeni rial chosen
    The Yemeni rial is the official monetary unit of Yemen, used for everyday transactions and issued by the Central Bank of Yemen.
  • B. South Yemeni dinar
    The South Yemeni dinar was the former official currency of the People's Democratic Republic of Yemen (South Yemen) prior to its unification with North Yemen.
  • C. Saudi riyal
    The Saudi riyal is the official monetary unit of Saudi Arabia, used nationwide for all financial transactions and pegged to the US dollar.
  • D. Aden rupee
    The Aden rupee was the former currency of the British-controlled port of Aden, used before being succeeded by the Aden shilling.
  • E. Omani rial
    The Omani rial is the official currency of Oman, known for its high value relative to most other world currencies.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4b3a6e08190ae663701f50fab8e completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69f48691c8190af0ac959e92e10d9 completed April 20, 2026, 9:48 p.m.
Created at: April 16, 2026, 11:37 a.m.