Triple
T4122986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahraini dinar |
E92656
|
entity |
| Predicate | pegRateApprox |
P52365
|
FINISHED |
| Object | 1 BHD ≈ 2.65957 USD |
—
|
LITERAL 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: 1 BHD ≈ 2.65957 USD | Statement: [Bahraini dinar, pegRateApprox, 1 BHD ≈ 2.65957 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pegRateApprox Context triple: [Bahraini dinar, pegRateApprox, 1 BHD ≈ 2.65957 USD]
-
A.
pegRate
chosen
Indicates a fixed or controlled exchange rate at which one currency is pegged to another or to a reference value.
-
B.
pegRatio
Indicates the relationship between a company’s price-to-earnings (P/E) ratio and its expected earnings growth rate, expressing how highly the market values each unit of anticipated growth.
-
C.
maximumBitrate
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
D.
typicalResolution
Indicates the usual or standard level of detail or clarity at which something (such as an image, display, or representation) is normally rendered or presented.
-
E.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
- F. None of above.
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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.