Triple
T2444695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icelandic króna |
E53361
|
entity |
| Predicate | usedInAccountingStandard |
P36097
|
FINISHED |
| Object | Icelandic financial reporting |
—
|
LITERAL 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: Icelandic financial reporting | Statement: [Icelandic króna, usedInAccountingStandard, Icelandic financial reporting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAccountingStandard Context triple: [Icelandic króna, usedInAccountingStandard, Icelandic financial reporting]
-
A.
usedInFinancialDocuments
chosen
Indicates that something is employed or appears within financial documents or records.
-
B.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
C.
usedInTaxPayments
Indicates that something is employed or applied as part of making or fulfilling tax payments.
-
D.
usedInInternationalBankingCode
Indicates that something is employed as part of an internationally recognized banking identification or transaction code.
-
E.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
- F. None of above.
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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.