Triple
T3582948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish markka |
E75842
|
entity |
| Predicate | usedAsBookkeepingCurrencyUntil |
P7629
|
FINISHED |
| Object | 2001-12-31 |
—
|
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: 2001-12-31 | Statement: [Finnish markka, usedAsBookkeepingCurrencyUntil, 2001-12-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsBookkeepingCurrencyUntil Context triple: [Finnish markka, usedAsBookkeepingCurrencyUntil, 2001-12-31]
-
A.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
-
B.
successorCurrenciesUsed
Indicates that the currencies referenced have been used as successor currencies replacing a previous currency in use.
-
C.
coexistedWithCurrency
Indicates that one currency was in circulation at the same time as another currency.
-
D.
previousCurrency
Indicates that one currency served as the predecessor or was replaced by another currency in a monetary system or sequence.
-
E.
legalTenderUntil
chosen
Indicates that a form of money is officially recognized as valid payment only up to a specified date or 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc104846c81908b6fbde7061464b4 |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.