Triple
T25310560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pengő |
E634595
|
entity |
| Predicate | exchangeToForintContext |
P128191
|
FINISHED |
| Object | post-hyperinflation stabilization |
—
|
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: post-hyperinflation stabilization | Statement: [pengő, exchangeToForintContext, post-hyperinflation stabilization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeToForintContext Context triple: [pengő, exchangeToForintContext, post-hyperinflation stabilization]
-
A.
currencyContext
Indicates that a particular monetary value or transaction is expressed, interpreted, or valid within a specified currency framework or setting.
-
B.
currencyTransition
chosen
Indicates a change from one currency to another within a transaction, system, or context.
-
C.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
-
D.
exchangeCurrency
Indicates a relationship where one party converts or trades an amount of one currency for an equivalent amount of another currency.
-
E.
valueRelativeToAkçe
Indicates the value of something expressed in terms of, or relative to, the akçe monetary unit.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4939e84dc8190bef761d9bfee08a6 |
completed | May 1, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:26 p.m.