Triple
T20293787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libyan pound |
E510093
|
entity |
| Predicate | exchangeRateToLibyanDinar |
P92667
|
FINISHED |
| Object | 1 Libyan pound = 1 Libyan dinar |
—
|
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 Libyan pound = 1 Libyan dinar | Statement: [Libyan pound, exchangeRateToLibyanDinar, 1 Libyan pound = 1 Libyan dinar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeRateToLibyanDinar Context triple: [Libyan pound, exchangeRateToLibyanDinar, 1 Libyan pound = 1 Libyan dinar]
-
A.
exchangeRateToPoundSterling
Indicates the rate at which one unit of a given currency can be converted into British pounds sterling.
-
B.
currencyExchangeRate
chosen
Indicates the rate at which one currency can be exchanged for another.
-
C.
exchangeCurrency
Indicates a relationship where one party converts or trades an amount of one currency for an equivalent amount of another currency.
-
D.
exchangeRateAtDollarization
Indicates the exchange rate that was in effect at the time a currency or economy underwent dollarization.
-
E.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
- 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67704262c8190bc903b733d849881 |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:13 a.m.