Triple
T22729110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RJBT |
E562080
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Tajima Airport |
—
|
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: Tajima Airport | Statement: [RJBT, locatedIn, Tajima Airport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tajima Airport Context triple: [RJBT, locatedIn, Tajima Airport]
-
A.
Tajima Airport
chosen
Tajima Airport is a regional airport in northern Hyogo Prefecture, Japan, primarily serving domestic flights and connecting the Tajima area with major Japanese cities.
-
B.
Moruya Airport
Moruya Airport is a regional airport in New South Wales, Australia, providing air transport services for the town of Moruya and the surrounding Eurobodalla region.
-
C.
Osubi Airport
Osubi Airport is a domestic airport serving the city of Warri and its surrounding region in Delta State, Nigeria.
-
D.
Kitadaitō Airport
Kitadaitō Airport is a small regional airport in Okinawa Prefecture, Japan, providing air access to the remote island of Kitadaitōjima.
-
E.
Nakashibetsu Airport
Nakashibetsu Airport is a regional airport in eastern Hokkaido, Japan, serving as an air gateway to the Nemuro and Shiretoko areas.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792be7d88190b6d7d79041fcba25 |
completed | April 29, 2026, 3:21 a.m. |
Created at: April 17, 2026, 3:21 p.m.