Triple

T22295582
Position Surface form Disambiguated ID Type / Status
Subject Sørvágur E551109 entity
Predicate usesCurrency P188 FINISHED
Object Danish krone NE NERFINISHED

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: Danish krone | Statement: [Sørvágur, usesCurrency, Danish krone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Danish krone
Context triple: [Sørvágur, usesCurrency, Danish krone]
  • 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. Danish Crown
    Danish Crown was the historical monarchy of Denmark, which ruled over Danish territories and overseas possessions, including colonial forts such as Fort Kongenstein.
  • 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. 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 (2 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_69e11e45fb848190a1b2ae21296e3a5f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1571fe76c8190a40b3679802a5475 completed April 29, 2026, 12:56 a.m.
Created at: April 16, 2026, 8:41 p.m.