Triple

T12851512
Position Surface form Disambiguated ID Type / Status
Subject Muanda Airport E307332 entity
Predicate IATAcode P418 FINISHED
Object MNB E634592 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: MNB | Statement: [Muanda Airport, IATAcode, MNB]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MNB
Context triple: [Muanda Airport, IATAcode, MNB]
  • A. MNB chosen
    MNB is the central bank of Hungary, responsible for the country’s monetary policy, financial stability, and issuance of the national currency.
  • B. BNM
    BNM is the central bank of Malaysia, responsible for issuing currency, formulating monetary policy, and overseeing the country’s financial system.
  • C. NBU
    NBU is the central bank of Ukraine, responsible for the country’s monetary policy, currency stability, and regulation of the banking system.
  • D. NBU
    NBU is the former IATA airport code for Naval Air Station Glenview, a decommissioned U.S. Navy air station in Illinois.
  • E. NBK
    NBK is the central bank of Kazakhstan, responsible for the country’s monetary policy, financial stability, and regulation of the banking sector.
  • 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_69d7bdf5e7cc8190be357278bc5ba3bb completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d97020eacc81909357b3398d17dc49 completed April 10, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f69ba5059c81908be3b8b371518f41 completed May 3, 2026, 12:49 a.m.
Created at: April 9, 2026, 5:36 p.m.