Triple

T15475199
Position Surface form Disambiguated ID Type / Status
Subject rigsdaler E376765 entity
Predicate governingAuthority P46 FINISHED
Object Danish crown 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 crown | Statement: [rigsdaler, governingAuthority, Danish crown]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Danish crown
Context triple: [rigsdaler, governingAuthority, Danish crown]
  • A. 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.
  • 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 krone chosen
    The Danish krone is the official currency of Denmark, known for its stable value and close peg to the euro.
  • 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_69d85cd21dcc81908646251b1c26ea00 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03f6e859481909c3d08343b7ad27c completed April 16, 2026, 1:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff36595bfc8190a0d60b3cb875ccc5 completed May 9, 2026, 1:27 p.m.
Created at: April 10, 2026, 3:34 a.m.