Triple
T1973908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burkina Faso |
E42862
|
entity |
| Predicate | currencyCode |
P208
|
FINISHED |
| Object | XOF |
E122066
|
NE 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: XOF | Statement: [Burkina Faso, currencyCode, XOF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XOF Context triple: [Burkina Faso, currencyCode, XOF]
-
A.
XOF
chosen
XOF is the West African CFA franc, a regional currency used by several West African countries including Niger.
-
B.
XAF
XAF is the currency code for the Central African CFA franc, a regional currency used by several Central African countries.
-
C.
XPF
XPF is the CFP franc, a currency used in several French overseas collectivities in the Pacific, including French Polynesia.
-
D.
OX
OX is the postcode area covering Oxford and its surrounding region in Oxfordshire, England.
-
E.
XUA
XUA (Cross-Enterprise User Assertion) is an IHE IT Infrastructure profile that standardizes how user identity and authentication information is securely communicated across healthcare enterprises.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f6c4208190a41e02733faed8df |
completed | March 7, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae03256a6c81909885fc3618c9c009 |
completed | March 8, 2026, 11:15 p.m. |
Created at: March 4, 2026, 7:36 p.m.