Triple

T6352103
Position Surface form Disambiguated ID Type / Status
Subject Faroese E142895 entity
Predicate usesCurrency P188 FINISHED
Object Danish krone 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: Danish krone | Statement: [Faroese, usesCurrency, Danish krone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Danish krone
Context triple: [Faroese, 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. 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–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.
  • E. Swedish krona
    The Swedish krona is the official currency of Sweden, used for everyday transactions and major national and international payments.
  • 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_69c008d6dcbc8190aa1c2f1fd8916b42 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c067dd3c74819085a164b750094c46 completed March 22, 2026, 10:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69c604546ed08190bb1c89bc5461f5cd completed March 27, 2026, 4:15 a.m.
Created at: March 22, 2026, 4:31 p.m.