Triple

T1322754
Position Surface form Disambiguated ID Type / Status
Subject Reykjavík E28255 entity
Predicate currency P245 FINISHED
Object Icelandic króna E53361 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: Icelandic króna | Statement: [Reykjavík, currency, Icelandic króna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Icelandic króna
Context triple: [Reykjavík, currency, Icelandic króna]
  • A. Icelandic króna chosen
    The Icelandic króna is the official national currency of Iceland, used for all domestic financial transactions and issued by the Central Bank of Iceland.
  • B. Estonian kroon
    The Estonian kroon was the former national currency of Estonia, used from 1992 until the country adopted the euro in 2011.
  • C. Danish krone
    The Danish krone is the official currency of Denmark, known for its stable value and close peg to the euro.
  • D. Swedish krona
    The Swedish krona is the official currency of Sweden, used for everyday transactions and major national and international payments.
  • E. Norwegian krone
    The Norwegian krone is the official monetary unit of Norway, issued by Norges Bank and commonly traded under the currency code NOK.
  • 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_69a498540a2481909e807a762280d3ba completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c19b76b48190aa8857b80971a842 completed March 1, 2026, 10:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69acbafabec08190a18c5fd23e2b833c completed March 7, 2026, 11:55 p.m.
Created at: March 1, 2026, 7:55 p.m.