Triple
T5443132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Bureau of Meteorology |
E122184
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | BoM |
E521447
|
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: BoM | Statement: [Australian Bureau of Meteorology, abbreviation, BoM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BoM Context triple: [Australian Bureau of Meteorology, abbreviation, BoM]
-
A.
BoM
chosen
BoM is Australia’s national weather, climate, and water agency responsible for forecasting, warnings, and environmental monitoring.
-
B.
BOG
BOG is the IATA airport code for El Dorado International Airport, the main international gateway serving Bogotá, Colombia.
-
C.
BOL
BOL is the three-letter ISO 3166-1 alpha-3 country code assigned to Bolivia.
-
D.
BOA
BOA is the abbreviation commonly used for the British Olympic Association, the National Olympic Committee responsible for Great Britain and Northern Ireland’s participation in the Olympic Games.
-
E.
Bou
Bou is a surname of Spanish origin borne by Argentine professional footballer Gustavo Bou, among others.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd91cb5eec8190bdf2ef0bdea84a62 |
completed | March 20, 2026, 6:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf487fdfe08190af6294021d1b81e5 |
completed | March 22, 2026, 1:40 a.m. |
Created at: March 20, 2026, 2:07 p.m.