Triple
T16961006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICAO airport code system |
E411425
|
entity |
| Predicate | identifierExample |
P3732
|
FINISHED |
| Object | RJTT |
E186915
|
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: RJTT | Statement: [ICAO airport code system, identifierExample, RJTT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RJTT Context triple: [ICAO airport code system, identifierExample, RJTT]
-
A.
RJTT
chosen
RJTT is the ICAO airport code for Tokyo International Airport, commonly known as Haneda Airport, one of Japan’s primary airports serving the Tokyo metropolitan area.
-
B.
RJT
RJT is the IATA airport code assigned to Iruma Air Base, a military airfield in Saitama Prefecture, Japan.
-
C.
RJT
RJT is the station code for Rajkot Junction, a major railway station serving the city of Rajkot in Gujarat, India.
-
D.
JRTT
JRTT is a Japanese government agency responsible for railway construction, transportation infrastructure development, and related technological advancement.
-
E.
RJTA
RJTA is the ICAO airport code for Naval Air Facility Atsugi, a joint U.S.–Japan military air base in Kanagawa Prefecture, 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0209a9081909d9c62456bc16e14 |
completed | April 18, 2026, 6:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d46ad58c8190be9f0b36daba8162 |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:31 a.m.