Triple
T15490093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazzaville Maya-Maya Airport |
E378658
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | BZV |
E378653
|
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: BZV | Statement: [Brazzaville Maya-Maya Airport, IATAcode, BZV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BZV Context triple: [Brazzaville Maya-Maya Airport, IATAcode, BZV]
-
A.
BZV
chosen
BZV is the IATA airport code for Maya-Maya Airport, the main international airport serving Brazzaville in the Republic of the Congo.
-
B.
BZ
BZ is the two-letter ISO 3166-1 alpha-2 country code assigned to Belize.
-
C.
BZ
BZ is the commonly used abbreviation for the Ministry of Foreign Affairs of the Netherlands, which is responsible for the country’s foreign policy and international relations.
-
D.
BZ
BZ is the vehicle registration code used for the district and city of Bautzen in the German state of Saxony.
-
E.
BZ
BZ is the vehicle registration code used on license plates for the municipality of Rammenau in Germany.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fac2af88190ac1d119e6b21dbe0 |
completed | April 16, 2026, 1:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff3d4661088190bb53161247effcc4 |
completed | May 9, 2026, 1:57 p.m. |
Created at: April 10, 2026, 3:48 a.m.