Triple
T1702773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BGN |
E36804
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | BGN |
E36804
|
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: BGN | Statement: [BGN, abbreviation, BGN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BGN Context triple: [BGN, abbreviation, BGN]
-
A.
BGN
chosen
BGN is the standard abbreviation for the U.S. Board on Geographic Names, the federal body that maintains uniform geographic name usage across the United States government.
-
B.
BG
BG is the two-letter ISO 3166-1 alpha-2 country code representing Bulgaria.
-
C.
BnG
BnG is the commonly used abbreviation for Bòrd na Gàidhlig, the principal public body responsible for promoting and supporting the Scottish Gaelic language in Scotland.
-
D.
BGY
BGY is the IATA airport code for Milan Bergamo Airport, a major low-cost and regional air travel hub serving the Milan metropolitan area in northern Italy.
-
E.
BEG
BEG is the IATA airport code for Belgrade Nikola Tesla Airport, the main international airport serving Serbia’s capital city.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa62f0eb408190809d1f6496d38e0b |
completed | March 6, 2026, 5:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad8acc65588190b09cc3528ff19653 |
completed | March 8, 2026, 2:42 p.m. |
Created at: March 4, 2026, 7:30 p.m.