Triple
T3882183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOK |
E92848
|
entity |
| Predicate | isNotEuroMemberCurrency |
P52126
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NOK, isNotEuroMemberCurrency, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotEuroMemberCurrency Context triple: [NOK, isNotEuroMemberCurrency, true]
-
A.
isWorldTradeCurrency
Indicates that a currency is officially used and widely accepted as a medium of exchange in international trade and global financial transactions.
-
B.
monetaryUnionPartner
Indicates that two entities are members of the same monetary union, sharing a common currency or coordinated monetary policy.
-
C.
eurozoneMember
Indicates that an entity is a country that belongs to the Eurozone, i.e., it uses the euro as its official currency within the European Union’s monetary union.
-
D.
usesExchangeRateRegime
Indicates that one entity adopts or operates under a particular exchange rate regime in conducting its currency or monetary arrangements.
-
E.
currencyArea
Indicates that one entity is the geographic or economic region in which the other entity’s currency is officially used or valid.
- F. None of above. chosen
Provenance (4 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:20 p.m.