Triple
T6991016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Monetary Area |
E162084
|
entity |
| Predicate | typeOfPeg |
P74319
|
FINISHED |
| Object | fixed exchange rate to South African rand |
—
|
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: fixed exchange rate to South African rand | Statement: [Common Monetary Area, typeOfPeg, fixed exchange rate to South African rand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPeg Context triple: [Common Monetary Area, typeOfPeg, fixed exchange rate to South African rand]
-
A.
typicalPegRange
Indicates the usual or standard range of peg values within which something is normally maintained or expected to operate.
-
B.
pouchType
Indicates the specific kind or category of pouch associated with an entity.
-
C.
typeOfFigure
Indicates that one entity is a specific kind or category of geometric figure relative to another.
-
D.
plateType
Indicates the specific category or style of plate associated with an item or context.
-
E.
partOfType
Indicates that one entity represents a component, segment, or subset that belongs to or is included within the type or category represented by another entity.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc08758819083d36a1fc0463b27 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6dbbc00fc8190a18221524b774021 |
completed | March 27, 2026, 7:34 p.m. |
Created at: March 27, 2026, 2:32 p.m.