Triple

T16081225
Position Surface form Disambiguated ID Type / Status
Subject Yanbu Airport E390113 entity
Predicate usesCurrency P188 FINISHED
Object Saudi riyal E40063 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: Saudi riyal | Statement: [Yanbu Airport, usesCurrency, Saudi riyal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saudi riyal
Context triple: [Yanbu Airport, usesCurrency, Saudi riyal]
  • A. Saudi riyal chosen
    The Saudi riyal is the official monetary unit of Saudi Arabia, used nationwide for all financial transactions and pegged to the US dollar.
  • B. Hejaz riyal
    The Hejaz riyal was the historical monetary unit used in the early 20th century in the Kingdom of Hejaz, in the western Arabian Peninsula.
  • C. Qatari riyal
    The Qatari riyal is the official national currency of Qatar, issued by the Qatar Central Bank and commonly used in all financial transactions throughout the country.
  • D. Dubai riyal
    The Dubai riyal was a former currency used in Dubai and some neighboring Trucial States before being replaced by the United Arab Emirates dirham.
  • E. Qatari dirham
    The Qatari dirham is a fractional monetary unit used as a subunit of Qatar’s national currency.
  • 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_69d86daf32ec8190a8c0466c8f49c3c0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1844a5c68819086a13c93a787b436 completed April 17, 2026, 12:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffeb917b008190b1680b347cfa0892 completed May 10, 2026, 2:21 a.m.
Created at: April 10, 2026, 4:57 a.m.