Triple
T17722025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MDBA |
E442360
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | MDBA |
—
|
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: MDBA | Statement: [MDBA, abbreviation, MDBA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MDBA Context triple: [MDBA, abbreviation, MDBA]
-
A.
MDBA
chosen
MDBA is the acronym for the Murray–Darling Basin Authority, the Australian government agency responsible for managing the Murray–Darling Basin’s water resources.
-
B.
Mdb
Mdb is the official station code used to identify Middelburg railway station in the Netherlands’ rail network.
-
C.
MDBs
MDBs are international financial institutions that provide loans, grants, and technical assistance to support economic and social development in multiple countries.
-
D.
MAB
MAB is a German vehicle registration code used for cars registered in the Erzgebirgskreis district of Saxony.
-
E.
MAB
MAB is a German bibliographic data format used for cataloging and exchanging library records, closely related to and historically aligned with MARC standards.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47486438c8190abe27eb4eb2c6fdf |
completed | April 19, 2026, 6:21 a.m. |
Created at: April 10, 2026, 10:07 a.m.