Triple

T353332
Position Surface form Disambiguated ID Type / Status
Subject Sweden E7489 entity
Predicate currency P245 FINISHED
Object Swedish krona E8255 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: Swedish krona | Statement: [Sweden, currency, Swedish krona]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Swedish krona
Context triple: [Sweden, currency, Swedish krona]
  • A. Swedish krona chosen
    The Swedish krona is the official currency of Sweden, used for everyday transactions and major national and international payments.
  • B. Danish krone
    The Danish krone is the official currency of Denmark, known for its stable value and close peg to the euro.
  • C. Norwegian krone
    The Norwegian krone is the official monetary unit of Norway, issued by Norges Bank and commonly traded under the currency code NOK.
  • D. Swiss franc
    The Swiss franc is the official currency of Switzerland and Liechtenstein, known for its stability and status as a major global reserve currency.
  • E. Slovak koruna
    The Slovak koruna was the former national currency of Slovakia, used both during the World War II-era Slovak state and later in the modern Slovak Republic until it was replaced by the euro.
  • 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_69a2e7e696948190bebc966535995e45 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eb80f524819093f4c2c18c3d615f completed Feb. 28, 2026, 1:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3dd353b488190b6ed966290260806 completed March 1, 2026, 6:31 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.