Triple

T30976665
Position Surface form Disambiguated ID Type / Status
Subject Hokkaido Air Commuter E789249 entity
Predicate focusCity P164 FINISHED
Object Okushiri Airport
Okushiri Airport is a small regional airport on Okushiri Island in Hokkaido, Japan, providing local air connections primarily served by Hokkaido Air Commuter.
E1971050 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: Okushiri Airport | Statement: [Hokkaido Air Commuter, focusCity, Okushiri Airport]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Okushiri Airport
Triple: [Hokkaido Air Commuter, focusCity, Okushiri Airport]
Generated description
Okushiri Airport is a small regional airport on Okushiri Island in Hokkaido, Japan, providing local air connections primarily served by Hokkaido Air Commuter.

Provenance (5 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_69f224c4831c8190be53924ec25a150a completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f693b92cb48190b1f354d3ca38375c completed May 3, 2026, 12:15 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b79ad4f248190844af3d093c3623e completed June 12, 2026, 3:14 a.m.
NEDg Description generation batch_6a2b7ae829ac8190816c4c7ffdfc3a1c completed June 12, 2026, 3:20 a.m.
NED2 Entity disambiguation (via description) batch_6a2b7bdca59c81909eeabf535985fd97 completed June 12, 2026, 3:24 a.m.
Created at: April 29, 2026, 8:55 p.m.