Triple

T23127683
Position Surface form Disambiguated ID Type / Status
Subject Palangka Raya E577077 entity
Predicate hasAirport P105 FINISHED
Object Tjilik Riwut 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: Tjilik Riwut Airport | Statement: [Palangka Raya, hasAirport, Tjilik Riwut Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tjilik Riwut Airport
Context triple: [Palangka Raya, hasAirport, Tjilik Riwut Airport]
  • A. Tjilik Riwut Airport chosen
    Tjilik Riwut Airport is a public airport serving Palangka Raya in Central Kalimantan, Indonesia, functioning as a key regional hub for passenger and cargo air traffic.
  • B. Mutiara Airport
    Mutiara Airport is a public airport in Palu, Central Sulawesi, Indonesia, serving as the main air gateway to the region.
  • C. Jumandy Airport
    Jumandy Airport is a regional airport serving the city of Tena and the surrounding Amazonian area in Ecuador.
  • D. Pangsuma Airport
    Pangsuma Airport is a regional airport serving the town of Putussibau in West Kalimantan, Indonesia.
  • E. Radin Inten II Airport
    Radin Inten II Airport is a public airport serving the Bandar Lampung area in Lampung Province, Sumatra, Indonesia.
  • 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_69e245f7b0e481909c473ff4e6a54e2c completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18e55aa38819092816ffc52e20dbe completed April 29, 2026, 4:51 a.m.
Created at: April 17, 2026, 3:59 p.m.