Triple

T10428621
Position Surface form Disambiguated ID Type / Status
Subject Flesberg E245849 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: [Flesberg, usesCurrency, Norwegian krone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Norwegian krone
Context triple: [Flesberg, 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. 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.
  • C. Danish krone
    The Danish krone is the official currency of Denmark, known for its stable value and close peg to the euro.
  • D. Danish rigsdaler
    The Danish rigsdaler was Denmark’s former currency used until the 19th century, when it was superseded by the Danish krone.
  • 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_69d381bf3dc08190bf35a2643e4e8f22 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4ea4b4b5881908ae23f8efeea482b completed April 7, 2026, 11:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69d8dc374f6c8190a44b9da27be343e4 completed April 10, 2026, 11:17 a.m.
Created at: April 6, 2026, 12:13 p.m.