Triple
T1895326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansai International Airport |
E41967
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | RJBB |
E41968
|
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: RJBB | Statement: [Kansai International Airport, ICAO code, RJBB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RJBB Context triple: [Kansai International Airport, ICAO code, RJBB]
-
A.
RJBB
chosen
RJBB is the ICAO airport code for Kansai International Airport, a major international hub built on an artificial island in Osaka Bay, Japan.
-
B.
RJBE
RJBE is the ICAO airport code for Kobe Airport, a regional airport serving the city of Kobe in Japan.
-
C.
RJ
RJ is the two-letter IATA airline designator assigned to Royal Jordanian, the flag carrier airline of Jordan.
-
D.
RJOO
RJOO is the ICAO airport code for Osaka International Airport, a major domestic aviation hub serving the Osaka metropolitan area in Japan.
-
E.
RJAA
RJAA is the ICAO airport code for Narita International Airport, a major international gateway serving the Tokyo metropolitan area in Japan.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adeaebd5ec8190897619628f7b821d |
completed | March 8, 2026, 9:32 p.m. |
Created at: March 4, 2026, 7:35 p.m.