Triple
T12740036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for the Lira |
E304464
|
entity |
| Predicate | targetExchangeRate |
P92667
|
FINISHED |
| Object | 90 lire to the British pound |
—
|
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: 90 lire to the British pound | Statement: [Battle for the Lira, targetExchangeRate, 90 lire to the British pound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetExchangeRate Context triple: [Battle for the Lira, targetExchangeRate, 90 lire to the British pound]
-
A.
currencyExchangeRate
chosen
Indicates the rate at which one currency can be exchanged for another.
-
B.
referenceForExchangeRates
Indicates that something serves as the authoritative source or benchmark used to determine or look up exchange rates between currencies.
-
C.
exchangeCurrency
Indicates a relationship where one party converts or trades an amount of one currency for an equivalent amount of another currency.
-
D.
exchangeRateToPoundSterling
Indicates the rate at which one unit of a given currency can be converted into British pounds sterling.
-
E.
exchangeRatio
Indicates the proportional rate at which one entity, resource, or value can be exchanged for another.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.