Triple

T18976076
Position Surface form Disambiguated ID Type / Status
Subject Ranchi Airport E464299 entity
Predicate alsoKnownAs P39 FINISHED
Object Birsa Munda 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: Birsa Munda Airport | Statement: [Ranchi Airport, alsoKnownAs, Birsa Munda Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Birsa Munda Airport
Context triple: [Ranchi Airport, alsoKnownAs, Birsa Munda Airport]
  • A. Birsa Munda Airport chosen
    Birsa Munda Airport is the main domestic airport serving Ranchi and the surrounding region in the Indian state of Jharkhand.
  • B. Bilasa Devi Kevat Airport
    Bilasa Devi Kevat Airport is a regional domestic airport serving the city of Bilaspur in the Indian state of Chhattisgarh.
  • C. Kumbhirgram Airport
    Kumbhirgram Airport is a domestic airport serving the city of Silchar in the Indian state of Assam.
  • D. Mohanbari Airport
    Mohanbari Airport is a regional airport serving the Upper Assam area of northeastern India, providing air connectivity for passengers and cargo.
  • E. Ghat Airport
    Ghat Airport is a small regional airport serving the town of Ghat in southwestern Libya, primarily handling domestic flights.
  • 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_69d8dd008af48190a97ff1c6488edf1b completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d61f96c88190b9a25158e0b012ca completed April 20, 2026, 7:30 a.m.
Created at: April 10, 2026, noon