Triple
T28801262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaguchi Ube–Tokyo Haneda |
E727240
|
entity |
| Predicate | ICAODestinationCode |
P419
|
FINISHED |
| Object | RJTT |
—
|
NE NERFINISHED |
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: [Yamaguchi Ube–Tokyo Haneda, ICAODestinationCode, RJTT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ICAODestinationCode Context triple: [Yamaguchi Ube–Tokyo Haneda, ICAODestinationCode, RJTT]
-
A.
IATAcode
Indicates the three-letter IATA airport or airline code assigned to the entity.
-
B.
hasIATAcode
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
-
C.
icaoCodeType
Indicates that the relationship specifies or classifies the ICAO (International Civil Aviation Organization) code associated with an entity.
-
D.
ICAOcode
chosen
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
-
E.
portCodeLOCODE
Indicates that a port is identified by a specific LOCODE (Location Code) value.
- F. None of above.
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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:27 a.m.