Triple

T17752247
Position Surface form Disambiguated ID Type / Status
Subject Lithuanian talonas E443140 entity
Predicate replacedBy P101 FINISHED
Object Lithuanian litas NE NERFINISHED

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: Lithuanian litas | Statement: [Lithuanian talonas, replacedBy, Lithuanian litas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lithuanian litas
Context triple: [Lithuanian talonas, replacedBy, Lithuanian litas]
  • A. Lithuanian litas chosen
    The Lithuanian litas was the former national currency of Lithuania, used until the country adopted the euro in 2015.
  • B. Lithuanian grivna
    The Lithuanian grivna was a medieval silver ingot and unit of weight used as a basis for trade and taxation in the territories of the Grand Duchy of Lithuania.
  • C. Lithuanian talonas
    The Lithuanian talonas was a temporary currency used in Lithuania during the early 1990s transition from the Soviet ruble to the modern litas.
  • D. Latvian rublis
    The Latvian rublis was the transitional currency used in Latvia in the early 1990s between the collapse of the Soviet ruble system and the introduction of the Latvian lats.
  • E. Latvian lats
    The Latvian lats was the national currency of Latvia until it was replaced by the euro in 2014.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9edf16c8190a59ebd245d378f4f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4841b3ccc8190b3241b3e0fa4b2e8 completed April 19, 2026, 7:28 a.m.
Created at: April 10, 2026, 10:10 a.m.