Triple

T2570403
Position Surface form Disambiguated ID Type / Status
Subject Sk E57650 entity
Predicate hasCountrySuccessorCurrency P26139 FINISHED
Object euro in Slovakia 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: euro in Slovakia | Statement: [Sk, hasCountrySuccessorCurrency, euro in Slovakia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCountrySuccessorCurrency
Context triple: [Sk, hasCountrySuccessorCurrency, euro in Slovakia]
  • A. countrySucceededBy
    Indicates that one country is the direct successor state that replaces or follows another country in sovereignty or political continuity.
  • B. countryPredecessor
    Indicates that one country existed before and was succeeded or replaced by another country in a historical or political sense.
  • C. successorCurrenciesUsed chosen
    Indicates that the currencies referenced have been used as successor currencies replacing a previous currency in use.
  • D. formerCurrency
    Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
  • 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_69ab4a51410081908501dcf8bad9adc4 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd382928c8190b6316f3db48d8e73 completed March 7, 2026, 7:28 a.m.
PD Predicate disambiguation batch_69abd0ce4dcc8190b17a65abf9bd1bb0 completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:48 p.m.