Triple
T8542114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pula–thebe system |
E202221
|
entity |
| Predicate | currencyCodePrimaryUnit |
P39837
|
FINISHED |
| Object | BWP |
—
|
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: BWP | Statement: [pula–thebe system, currencyCodePrimaryUnit, BWP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyCodePrimaryUnit Context triple: [pula–thebe system, currencyCodePrimaryUnit, BWP]
-
A.
currencySubunitOf
Indicates that a monetary subunit (such as cents) is a fractional unit belonging to and defined in terms of a larger base currency.
-
B.
currencyCodeDenoted
chosen
Indicates that a specific currency code is used to denote or represent a particular currency.
-
C.
monetaryUnitOfAccount
Indicates that something serves as the standard unit in which the value of goods, services, and financial transactions is measured and recorded.
-
D.
ISO4217MinorUnit
Indicates the number of decimal places (minor currency units) used to represent amounts in the currency defined by the ISO 4217 standard.
-
E.
currencySignAdopted
Indicates that a particular currency sign has been officially adopted for use with a given currency or monetary system.
- 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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6e26be48190b10bc62fad178dad |
completed | March 31, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.