Triple
T33342074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CEMAC Treaty |
E853696
|
entity |
| Predicate | currencyFrameworkFor |
P245
|
FINISHED |
| Object | CFA franc BEAC |
—
|
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: CFA franc BEAC | Statement: [CEMAC Treaty, currencyFrameworkFor, CFA franc BEAC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyFrameworkFor Context triple: [CEMAC Treaty, currencyFrameworkFor, CFA franc BEAC]
-
A.
currencyForm
Indicates that one entity is a specific monetary form, denomination, or variant of the currency represented by the other entity.
-
B.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
C.
currency
chosen
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
D.
currencyPlanned
Indicates that a specific currency is intended or scheduled to be used in a planned transaction, budget, or financial arrangement.
-
E.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 1, 2026, 1:34 a.m.