Triple
T1791353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWP |
E39501
|
entity |
| Predicate | ISO4217Section |
P32422
|
FINISHED |
| Object | current currencies |
—
|
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: current currencies | Statement: [BWP, ISO4217Section, current currencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO4217Section Context triple: [BWP, ISO4217Section, current currencies]
-
A.
ISO4217CurrencyManaged
Indicates that an entity is responsible for administering, regulating, or overseeing a specific ISO 4217 currency.
-
B.
codeNumericISO4217
Indicates that an entity is associated with a specific ISO 4217 numeric currency code.
-
C.
formerISO4217Code
Indicates that an entity was previously assigned a particular ISO 4217 currency code that is no longer in current use for it.
-
D.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
E.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab75457e54819096b8c6ae8c65550c |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61d165688190924962a98e07ff69 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab75444d28819091c393e62fc97f82 |
completed | March 7, 2026, 12:45 a.m. |
Created at: March 4, 2026, 7:32 p.m.