Triple

T4649553
Position Surface form Disambiguated ID Type / Status
Subject Nasdaq Copenhagen E102258 entity
Predicate currencyCode P208 FINISHED
Object DKK E33163 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: DKK | Statement: [Nasdaq Copenhagen, currencyCode, DKK]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: DKK
Context triple: [Nasdaq Copenhagen, currencyCode, DKK]
  • A. Danish krone chosen
    The Danish krone is the official currency of Denmark, known for its stable value and close peg to the euro.
  • B. Danish rigsdaler
    The Danish rigsdaler was Denmark’s former currency used until the 19th century, when it was superseded by the Danish krone.
  • 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. Swedish krona
    The Swedish krona is the official currency of Sweden, used for everyday transactions and major national and international payments.
  • E. Swedish–Norwegian krone
    The Swedish–Norwegian krone was the common gold-based currency used by the united kingdoms of Sweden and Norway in the late 19th and early 20th centuries.
  • 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_69bd43d71a308190afea7280841b0de8 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd6300a3fc8190b39ee96d756a748e completed March 20, 2026, 3:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdfae3d8f4819082ec002bc4d9819d completed March 21, 2026, 1:56 a.m.
Created at: March 20, 2026, 1:14 p.m.