Triple
T14948309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Chitose Airport |
E372724
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | RJCC |
E372725
|
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: RJCC | Statement: [New Chitose Airport, ICAO code, RJCC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RJCC Context triple: [New Chitose Airport, ICAO code, RJCC]
-
A.
RJCC
chosen
RJCC is the ICAO airport code for New Chitose Airport, the main international gateway serving Sapporo and the Hokkaido region of Japan.
-
B.
RJCO
RJCO is the ICAO airport code for Okadama Airport in Sapporo, Japan.
-
C.
JCC
JCC is a public community college serving the Jamestown, New York region with two-year degree and certificate programs.
-
D.
BJCC
BJCC is a major multi-purpose convention, entertainment, and sports complex located in downtown Birmingham, Alabama.
-
E.
FJCC
FJCC was a major mid-20th-century U.S. computing conference that served as a key forum for presenting influential research and developments in computer science and technology.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded68e35c481908e47cd68441c5115 |
completed | April 15, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe7e986dfc8190a5cf363dabe6bdef |
completed | May 9, 2026, 12:23 a.m. |
Created at: April 10, 2026, 2:39 a.m.