Triple
T29235702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botswana thebe |
E741186
|
entity |
| Predicate | exchangeableFor |
P48011
|
FINISHED |
| Object | Botswana 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: Botswana pula | Statement: [Botswana thebe, exchangeableFor, Botswana pula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeableFor Context triple: [Botswana thebe, exchangeableFor, Botswana pula]
-
A.
exchangedFor
Indicates that one entity has been traded or substituted in return for another entity.
-
B.
exchanged
Indicates a reciprocal transfer of something (such as information, goods, or services) between two or more entities.
-
C.
isExchangedVia
Indicates that something is transferred or traded from one party to another through a specified medium, channel, or mechanism.
-
D.
exchangeableAtCentralBank
chosen
Indicates that something can be traded in or redeemed at a central bank, typically for another form of value such as legal tender.
-
E.
exchangeSegmentOf
Indicates that one entity gives a portion or segment of something to another entity, typically as part of a reciprocal transfer or trade.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664648f388190ae9988742d53bc89 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:29 p.m.