Triple
T5442006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kemi City Council |
E122155
|
entity |
| Predicate | usesBudgetCurrency |
P12066
|
FINISHED |
| Object | euro |
—
|
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: euro | Statement: [Kemi City Council, usesBudgetCurrency, euro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBudgetCurrency Context triple: [Kemi City Council, usesBudgetCurrency, euro]
-
A.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
B.
usesCurrencyInitially
Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
-
C.
currencyPlanned
chosen
Indicates that a specific currency is intended or scheduled to be used in a planned transaction, budget, or financial arrangement.
-
D.
usesSupplementaryCurrency
Indicates that an entity employs an additional, non-primary currency alongside its main currency for transactions or value exchange.
-
E.
currencyOfPurse
Indicates the type of currency that is contained in or associated with a given purse.
- 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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.