Triple

T1282606
Position Surface form Disambiguated ID Type / Status
Subject Knivsta Municipality E27359 entity
Predicate usesCurrency P188 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: [Knivsta Municipality, usesCurrency, Swedish krona]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Swedish krona
Context triple: [Knivsta Municipality, usesCurrency, 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. Finnish markka
    The Finnish markka was the national currency of Finland until it was replaced by the euro in 2002.
  • D. Norwegian krone
    The Norwegian krone is the official monetary unit of Norway, issued by Norges Bank and commonly traded under the currency code NOK.
  • E. Estonian kroon
    The Estonian kroon was the former national currency of Estonia, used from 1992 until the country adopted the euro in 2011.
  • 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_69a496d3710c8190955dee8bc0dacb50 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c0b47be08190828a1c0a11d94ce8 completed March 1, 2026, 10:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69acacba08f881909230c2d9459d4bc4 completed March 7, 2026, 10:54 p.m.
Created at: March 1, 2026, 7:50 p.m.