Triple
T29293810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miyazaki–Tokyo Haneda |
E742760
|
entity |
| Predicate | destinationAirportICAO |
P166813
|
FINISHED |
| Object | RJTT |
—
|
LITERAL 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: [Miyazaki–Tokyo Haneda, destinationAirportICAO, RJTT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destinationAirportICAO Context triple: [Miyazaki–Tokyo Haneda, destinationAirportICAO, RJTT]
-
A.
destinationAirportInvestigated
Indicates that an airport serving as a destination has been examined or analyzed, typically as part of an investigation or assessment process.
-
B.
destinationAirportOfHijackedFlight
Indicates the airport that served or was intended to serve as the destination of a hijacked flight.
-
C.
destinationAirportRole
Indicates the role an airport plays as the destination point within a given travel, flight, or route relationship.
-
D.
destinationAirportAtTimeOfCrash
Indicates the airport that was the intended destination of a flight at the time the crash occurred.
-
E.
typicalDestinationAirportIATA
Indicates the IATA airport code that is typically the destination in this kind of trip or route.
- F. None of above. chosen
Provenance (4 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66542901c8190a34ece2e73b93744 |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661e9cb308190a56e25dc17df248e |
completed | May 2, 2026, 8:43 p.m. |
Created at: April 28, 2026, 1:04 p.m.