Triple
T10262938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | krone |
E240643
|
entity |
| Predicate | ISO4217CodeExample |
P86254
|
FINISHED |
| Object | SEK |
E46879
|
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: SEK | Statement: [krone, ISO4217CodeExample, SEK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SEK Context triple: [krone, ISO4217CodeExample, SEK]
-
A.
SEK
chosen
SEK is the official currency code for the Swedish krona, the national currency of Sweden.
-
B.
SE
SE is the official two-letter postal abbreviation for the Brazilian state of Sergipe.
-
C.
SE
SE is the two-letter ISO 3166-1 alpha-2 country code that uniquely identifies Sweden in international standards and systems.
-
D.
SE
SE is the standard abbreviation for a Societas Europaea, a public limited-liability company structure that allows firms to operate across European Union member states under a single legal form.
-
E.
SECA
SECA refers to designated maritime zones where strict limits are imposed on the sulfur content of ship fuel to reduce air pollution and protect human health and the environment.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4dfbfa26c8190b536655d33112ddf |
completed | April 7, 2026, 10:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6f7f81dd481909022efde8fc46e68 |
completed | April 9, 2026, 12:51 a.m. |
Created at: April 6, 2026, 11:32 a.m.