Triple
T28022277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bophuthatswana |
E707720
|
entity |
| Predicate | hadOwnCurrency |
P62524
|
FINISHED |
| Object | Bophuthatswana pula |
—
|
NE NERFINISHED |
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: Bophuthatswana pula | Statement: [Bophuthatswana, hadOwnCurrency, Bophuthatswana pula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadOwnCurrency Context triple: [Bophuthatswana, hadOwnCurrency, Bophuthatswana pula]
-
A.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
-
B.
usedAsCurrency
Indicates that something functions as money or a medium of exchange within an economic system.
-
C.
usesCurrencyInitially
Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
-
D.
wasDevaluedIn
Indicates that the value or worth of an entity was reduced during a specified event, time period, or context.
-
E.
introducedAsSeparateCurrency
chosen
Indicates that one currency was formally established and began circulating as a distinct, independent currency separate from a previously used or shared currency.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c0c0c408190ac9a9e10ad6466a8 |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:10 p.m.