Triple

T16405565
Position Surface form Disambiguated ID Type / Status
Subject Malaysian airport network E398415 entity
Predicate hasComponent P35 FINISHED
Object Miri Airport E988327 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: Miri Airport | Statement: [Malaysian airport network, hasComponent, Miri Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Miri Airport
Context triple: [Malaysian airport network, hasComponent, Miri Airport]
  • A. Miri Airport chosen
    Miri Airport is a domestic and regional airport serving the city of Miri in Sarawak, Malaysia, and acts as a key hub for air travel within northern Borneo.
  • B. Dabok Airport
    Dabok Airport is a domestic airport serving the city of Udaipur in Rajasthan, India, and is officially named Maharana Pratap Airport.
  • C. Kambalda Airport
    Kambalda Airport is a small regional airfield serving the mining town of Kambalda in Western Australia.
  • D. Labasa Airport
    Labasa Airport is a small domestic airport serving the town of Labasa on the Fijian island of Vanua Levu.
  • E. Ramingining Airport
    Ramingining Airport is a small regional airfield serving the remote Aboriginal community of Ramingining in the Northern Territory of Australia.
  • 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e327d2b4e48190b7153f198639e9cd completed April 18, 2026, 6:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a004f439d048190bf779cb263b7c7a7 completed May 10, 2026, 9:26 a.m.
Created at: April 10, 2026, 5:09 a.m.