Triple

T2207111
Position Surface form Disambiguated ID Type / Status
Subject Marker E50824 entity
Predicate usesCurrency P188 FINISHED
Object Norwegian krone E16810 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: Norwegian krone | Statement: [Marker, usesCurrency, Norwegian krone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Norwegian krone
Context triple: [Marker, usesCurrency, Norwegian krone]
  • A. Norwegian krone chosen
    The Norwegian krone is the official monetary unit of Norway, issued by Norges Bank and commonly traded under the currency code NOK.
  • B. Danish krone
    The Danish krone is the official currency of Denmark, known for its stable value and close peg to the euro.
  • C. Danish rigsdaler
    The Danish rigsdaler was Denmark’s former currency used until the 19th century, when it was superseded by the Danish krone.
  • D. Swedish krona
    The Swedish krona is the official currency of Sweden, used for everyday transactions and major national and international payments.
  • E. riksdaler
    The riksdaler was Sweden’s former national currency used for several centuries before being replaced by the Swedish krona in the late 19th century.
  • 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_69a88b06709c8190978fb2418470d1b6 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abbfcbb83081908d5b2f1603c7b4d2 completed March 7, 2026, 6:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae71b629088190a5228a2f68500bd5 completed March 9, 2026, 7:07 a.m.
Created at: March 4, 2026, 7:46 p.m.