Triple
T7248641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RJBE |
E156538
|
entity |
| Predicate | iataCode |
P2569
|
FINISHED |
| Object | UKB |
E156537
|
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: UKB | Statement: [RJBE, iataCode, UKB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: UKB Context triple: [RJBE, iataCode, UKB]
-
A.
UKB
UKB is the abbreviation commonly used for University Hospital Bonn, a major academic medical center in Bonn, Germany.
-
B.
UKB
chosen
UKB is the IATA airport code for Kobe Airport, a regional airport serving the city of Kobe in Japan.
-
C.
UKX
UKX is the stock market index code used to represent the FTSE 100, a benchmark index of the largest companies listed on the London Stock Exchange.
-
D.
UKBB
UKBB is the ICAO airport code designating Boryspil International Airport, the main international gateway serving Kyiv, Ukraine.
-
E.
NKGB
NKGB was a Soviet state security and intelligence agency that operated before the formation of the KGB, handling internal security, counterintelligence, and secret police functions.
- 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_69c68827b5e481908dc05e145b2c92d4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea763f208190af1210cd8d2a05c9 |
completed | March 27, 2026, 8:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e523149481909bbc7dd88046e8b0 |
completed | March 28, 2026, 2:26 p.m. |
Created at: March 27, 2026, 2:56 p.m.