Triple
T5600033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lithuanian litas |
E147095
|
entity |
| Predicate | officiallyReplacedByEuroDate |
P9579
|
FINISHED |
| Object | 2015-01-01 |
—
|
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: 2015-01-01 | Statement: [Lithuanian litas, officiallyReplacedByEuroDate, 2015-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officiallyReplacedByEuroDate Context triple: [Lithuanian litas, officiallyReplacedByEuroDate, 2015-01-01]
-
A.
nonCashEuroChangeoverDate
Indicates the date on which the transition to the euro occurred for non-cash transactions (such as accounting and electronic payments).
-
B.
startOfUseAsSoleGermanCurrency
Indicates the point in time when something first began to be used as the only official currency in Germany.
-
C.
euroChangeoverCashDate
chosen
Indicates the date on which a country or region officially switched its physical cash currency to the euro.
-
D.
monetaryUnionReplacedBy
Indicates that one monetary union has been succeeded or superseded by another monetary union.
-
E.
peggedToEuroSince
Indicates that the value of one currency or financial instrument has been fixed or tightly linked to the euro starting from a specific point in time.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020d936dc8190a2e599f1df9fdd91 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.