Triple
T11813993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbadian dollar |
E280949
|
entity |
| Predicate | purposeOfPeg |
P79
|
FINISHED |
| Object | maintain monetary stability in Barbados |
—
|
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: maintain monetary stability in Barbados | Statement: [Barbadian dollar, purposeOfPeg, maintain monetary stability in Barbados]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfPeg Context triple: [Barbadian dollar, purposeOfPeg, maintain monetary stability in Barbados]
-
A.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
B.
operationalPurpose
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational context.
-
C.
curvePurpose
Indicates that a curve exists or is defined for a particular purpose, function, or intended use.
-
D.
traditionalPurpose
Indicates that something serves a role, function, or use that is established by long-standing custom or tradition.
-
E.
encodingPurpose
Indicates the reason or intended use for which an encoding is created or applied.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.