Triple

T6999976
Position Surface form Disambiguated ID Type / Status
Subject forint E162310 entity
Predicate replacedCurrency P2867 FINISHED
Object pengő E634595 NE 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: pengő | Statement: [forint, replacedCurrency, pengő]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: pengő
Context triple: [forint, replacedCurrency, pengő]
  • A. pengő chosen
    The pengő was the former Hungarian currency used primarily between the World Wars and during World War II, notorious for experiencing one of the worst hyperinflations in history.
  • B. Eperjes
    Eperjes is a historic town in present-day Slovakia, known today as Prešov, which was one of the major urban centers of the former Upper Hungary region.
  • C. Penge
    Penge is a suburban district in southeast London known for its Victorian architecture and proximity to Crystal Palace.
  • D. Hungarian pengő
    The Hungarian pengő was the national currency of Hungary from 1927 until its replacement after World War II, notorious for experiencing one of the worst hyperinflation episodes in history.
  • E. Rábafüzes
    Rábafüzes is a small Hungarian village near the Austrian border, known as a key road and rail crossing point between the two countries.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c68857ffc08190857dc62cd5253777 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dc0e54c88190b092870f2d128510 completed March 27, 2026, 7:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69c775573c84819081f34ab2b14b700a completed March 28, 2026, 6:29 a.m.
Created at: March 27, 2026, 2:33 p.m.