Triple
T2435701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johannesburg Stock Exchange |
E52954
|
entity |
| Predicate | primaryCurrencyCode |
P12372
|
FINISHED |
| Object | ZAR |
—
|
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: ZAR | Statement: [Johannesburg Stock Exchange, primaryCurrencyCode, ZAR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCurrencyCode Context triple: [Johannesburg Stock Exchange, primaryCurrencyCode, ZAR]
-
A.
associatedCurrencyCode
chosen
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
-
B.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
C.
majorCurrencyPair
Indicates that the two currencies form a widely traded, highly liquid foreign-exchange pair considered significant in global markets.
-
D.
ISO4217CodeOfParentCurrency
Indicates that the subject is the ISO 4217 currency code corresponding to the parent currency of the object.
-
E.
previousCurrency
Indicates that one currency served as the predecessor or was replaced by another currency in a monetary system or sequence.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.