Triple
T21440178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Litas |
E528917
|
entity |
| Predicate | exchangeRateFixDate |
P37095
|
FINISHED |
| Object | 2002-02-02 |
—
|
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: 2002-02-02 | Statement: [Litas, exchangeRateFixDate, 2002-02-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeRateFixDate Context triple: [Litas, exchangeRateFixDate, 2002-02-02]
-
A.
exchangeRateFixingDate
chosen
Indicates the specific date on which an exchange rate is determined or fixed for use in a financial transaction or agreement.
-
B.
exchangeRateContinuity
Indicates that the exchange rate between two currencies changes smoothly over time or conditions, without abrupt jumps or discontinuities.
-
C.
replacedCurrencyDate
Indicates the date on which one currency was officially replaced by another.
-
D.
fixedExchangeRateToUSD
Indicates that the value of one currency is maintained at a constant, predetermined rate relative to the US dollar.
-
E.
currencyExchangeRate
Indicates the rate at which one currency 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b700237c8190bbcb4bedc4242719 |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 6:05 p.m.