Triple
T17331363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RJFK |
E420823
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | KOJ |
—
|
NE ONNED1 |
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: KOJ | Statement: [RJFK, IATACode, KOJ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KOJ Context triple: [RJFK, IATACode, KOJ]
-
A.
KOJ
chosen
KOJ is the three-letter IATA airport code for Kagoshima Airport in Kagoshima Prefecture, Japan.
-
B.
KO
KO is the New York Stock Exchange ticker symbol for The Coca-Cola Company, one of the world’s largest and most recognizable beverage corporations.
-
C.
KO
KO is the line symbol used to represent the Keiō New Line, a railway line in the Tokyo metropolitan area operated by Keio Corporation.
-
D.
KOZ
KOZ is the IATA airport code for Ouzinkie Airport, a public airport serving the community of Ouzinkie in Alaska, United States.
-
E.
Ko
Ko is a Japanese given-name element commonly used in female names, often carrying meanings like “child” depending on the kanji used.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d6870c8190989897aa6beba8ff |
completed | April 19, 2026, 2:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a019550d3bc8190bda76e83edc81063 |
finalizing | May 11, 2026, 8:37 a.m. |
Created at: April 10, 2026, 5:43 a.m.