Triple
T10247613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank of Central African States |
E240257
|
entity |
| Predicate | pegsCurrencyTo |
P19139
|
FINISHED |
| Object | euro |
—
|
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: euro | Statement: [Bank of Central African States, pegsCurrencyTo, euro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pegsCurrencyTo Context triple: [Bank of Central African States, pegsCurrencyTo, euro]
-
A.
currencyPeg
Indicates that one currency’s value is fixed or tightly linked to the value of another currency or a basket of currencies.
-
B.
pegTargetCurrency
chosen
Indicates that one currency’s value is fixed or tightly linked to the value of a specified target currency.
-
C.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
-
D.
currencyPlanned
Indicates that a specific currency is intended or scheduled to be used in a planned transaction, budget, or financial arrangement.
-
E.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:27 a.m.