Triple
T15841111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Market |
E384102
|
entity |
| Predicate | currency |
P245
|
FINISHED |
| Object | Swedish krona |
E8255
|
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: Swedish krona | Statement: [Main Market, currency, Swedish krona]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Swedish krona Context triple: [Main Market, currency, Swedish krona]
-
A.
Swedish krona
chosen
The Swedish krona is the official currency of Sweden, used for everyday transactions and major national and international payments.
-
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.
Finnish markka
The Finnish markka was the national currency of Finland until it was replaced by the euro in 2002.
-
E.
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.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e764088190afba6c5c1acf8199 |
completed | April 16, 2026, 8:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa13eab4881908794104508ba53af |
completed | May 9, 2026, 9:03 p.m. |
Created at: April 10, 2026, 4:50 a.m.