Triple

T10255205
Position Surface form Disambiguated ID Type / Status
Subject Aomori Prefecture E240442 entity
Predicate hasAirport P105 FINISHED
Object Aomori Airport E861567 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: Aomori Airport | Statement: [Aomori Prefecture, hasAirport, Aomori Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aomori Airport
Context triple: [Aomori Prefecture, hasAirport, Aomori Airport]
  • A. Aomori Airport chosen
    Aomori Airport is a regional airport in northern Honshu, Japan, serving the city of Aomori with domestic flights and limited international connections.
  • B. Hakodate Airport
    Hakodate Airport is a regional international airport in Hakodate, Hokkaido, Japan, serving domestic flights and limited international routes.
  • C. Sapporo Okadama Airport
    Sapporo Okadama Airport is a regional airport in Sapporo, Japan, primarily serving domestic flights within Hokkaido.
  • D. Tokachi-Obihiro Airport
    Tokachi-Obihiro Airport is a regional airport in Hokkaido, Japan, serving the city of Obihiro and the surrounding Tokachi area with domestic flights.
  • E. Akita Airport
    Akita Airport is a regional airport in Akita Prefecture, Japan, providing domestic flights and limited international services for the surrounding area.
  • 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_69d381a7e198819090280d5ab885d59e completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d24c69ac81908b4da53d13407ac8 completed April 7, 2026, 9:45 a.m.
NED1 Entity disambiguation (via context triple) batch_69d998671c1c8190be2012a3faf6ba35 completed April 11, 2026, 12:40 a.m.
Created at: April 6, 2026, 11:30 a.m.