Triple
T16091267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangladesh Bank |
E390361
|
entity |
| Predicate | currencyCode |
P208
|
FINISHED |
| Object | BDT |
E84457
|
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: BDT | Statement: [Bangladesh Bank, currencyCode, BDT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BDT Context triple: [Bangladesh Bank, currencyCode, BDT]
-
A.
BDT
chosen
BDT is the ISO 4217 currency code for the Bangladeshi taka, the official currency of Bangladesh.
-
B.
BDTC
BDTC refers to British Overseas Territories Citizenship, a form of British nationality held by people with close connections to the UK’s overseas territories.
-
C.
DBDT
DBDT is a renowned professional modern dance company based in Dallas, Texas, known for its diverse repertory and commitment to arts education and community outreach.
-
D.
BdE
BdE is the commonly used abbreviation for the Bank of Spain, the country’s central bank responsible for monetary policy and financial supervision.
-
E.
BDU
BDU is a military uniform type commonly associated with the standard camouflage combat attire used by the U.S. armed forces from the early 1980s through the mid-2000s.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1858d1264819099434d7201614d05 |
completed | April 17, 2026, 12:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffeb9550f0819092660f6c4b0d708e |
completed | May 10, 2026, 2:21 a.m. |
Created at: April 10, 2026, 4:59 a.m.