Triple
T16046847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polska Ludowa |
E389243
|
entity |
| Predicate | waluta |
P245
|
FINISHED |
| Object | złoty polski |
—
|
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: złoty polski | Statement: [Polska Ludowa, waluta, złoty polski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waluta Context triple: [Polska Ludowa, waluta, złoty polski]
-
A.
currency
chosen
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
B.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
-
C.
wasDevaluedIn
Indicates that the value or worth of an entity was reduced during a specified event, time period, or context.
-
D.
currencyOrEconomy
Indicates that there is a relationship involving the type, status, or characteristics of a currency or economic system associated with an entity.
-
E.
reintroducedCurrencyOf
Indicates that a currency has been brought back into use as legal tender in a particular country or region after having been previously replaced, discontinued, or suspended.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.