Triple
T26096449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arab Monetary Fund |
E658279
|
entity |
| Predicate | usesCurrencyAbbreviation |
P166140
|
FINISHED |
| Object | AAD |
—
|
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: AAD | Statement: [Arab Monetary Fund, usesCurrencyAbbreviation, AAD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCurrencyAbbreviation Context triple: [Arab Monetary Fund, usesCurrencyAbbreviation, AAD]
-
A.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
B.
usesCurrencyInitially
Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
-
C.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
D.
usesSupplementaryCurrency
Indicates that an entity employs an additional, non-primary currency alongside its main currency for transactions or value exchange.
-
E.
currencyPractice
Indicates the customary or standard way a particular currency is used, represented, or managed in transactions or economic contexts.
- F. None of above. chosen
Provenance (4 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 26, 2026, 7:51 p.m.