Triple
T7373796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Caledonian |
E170073
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | BR |
E265984
|
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: BR | Statement: [British Caledonian, IATAcode, BR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BR Context triple: [British Caledonian, IATAcode, BR]
-
A.
BR
chosen
BR is the IATA airline designator for EVA Air, a major Taiwanese international carrier based in Taoyuan.
-
B.
BR
BR is a postcode area in southeast London and parts of northwest Kent, covering towns such as Bromley and Beckenham.
-
C.
BR
BR is the two-letter ISO 3166-1 alpha-2 country code that uniquely identifies Brazil in international standards and systems.
-
D.
BR
BR is the commonly used abbreviation for Banco de la República, Colombia’s central bank responsible for monetary policy and currency issuance.
-
E.
BR
BR is the abbreviation for the Radiocommunication Bureau, the specialized ITU body responsible for managing global radio-frequency spectrum and satellite orbits.
- 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1a6643c81909d626c8b6a7a11fd |
completed | March 27, 2026, 9:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c83437dd28819088c17cfd7dea2e5b |
completed | March 28, 2026, 8:04 p.m. |
Created at: March 27, 2026, 3:07 p.m.