Triple
T12015271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristol Airport |
E286007
|
entity |
| Predicate | hasIATACode |
P2569
|
FINISHED |
| Object | BRS |
E281503
|
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: BRS | Statement: [Bristol Airport, hasIATACode, BRS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BRS Context triple: [Bristol Airport, hasIATACode, BRS]
-
A.
BRS
chosen
BRS is the IATA airport code for Bristol Airport, a major regional airport serving Bristol and the southwest of England.
-
B.
BRS
BRS is the acronym commonly used for Biotechnology Regulatory Services, a U.S. regulatory program overseeing the safe development and use of certain genetically engineered organisms.
-
C.
BRS
BRS is the abbreviation for British Road Services, the former state-owned road haulage operator in the United Kingdom.
-
D.
BRS Media
BRS Media is a media and technology company best known for operating and marketing innovative, media-focused internet domain extensions such as .fm and .am.
-
E.
BRL
BRL is the official currency code for the Brazilian real, the legal tender of Brazil.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d9b17881908894be80d7c1b64e |
completed | April 10, 2026, 2:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f48b4535f48190ac5b2cabb4daf4af |
completed | May 1, 2026, 11:15 a.m. |
Created at: April 8, 2026, 9:47 p.m.