Triple
T33719418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | state budget of Lithuania |
E863969
|
entity |
| Predicate | changedCurrencyOn |
P128191
|
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: [state budget of Lithuania, changedCurrencyOn, 2015-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedCurrencyOn Context triple: [state budget of Lithuania, changedCurrencyOn, 2015-01-01]
-
A.
replacedCurrency
Indicates that one currency has been superseded and no longer used because another currency has taken its place.
-
B.
currencyTransition
chosen
Indicates a change from one currency to another within a transaction, system, or context.
-
C.
replacedCurrencyCode
Indicates that one currency has been superseded or replaced by another currency, identified by its code.
-
D.
replacedCurrencyName
Indicates that one currency has been superseded and taken the place of another as the official or primary monetary unit.
-
E.
changedDenominationAfter
Indicates that an entity adopted a different denomination or affiliation following a specified prior denomination.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:44 a.m.