Triple

T12748998
Position Surface form Disambiguated ID Type / Status
Subject Thandwe E304681 entity
Predicate hasTransportConnection P845 FINISHED
Object Thandwe Airport E1002411 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: Thandwe Airport | Statement: [Thandwe, hasTransportConnection, Thandwe Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thandwe Airport
Context triple: [Thandwe, hasTransportConnection, Thandwe Airport]
  • A. Thandwe Airport chosen
    Thandwe Airport is a domestic airport in Myanmar that serves the coastal town of Thandwe and the nearby Ngapali Beach resort area.
  • B. Nyaung U Airport
    Nyaung U Airport is a domestic airport in central Myanmar that serves as the main air gateway for visitors to the ancient temple city of Bagan.
  • C. Lashio Airport
    Lashio Airport is a public domestic airport serving the town of Lashio in northern Shan State, Myanmar.
  • D. Mandalay International Airport
    Mandalay International Airport is the main international gateway serving Mandalay and central Myanmar, handling both domestic and international flights.
  • E. Myitkyina Airport
    Myitkyina Airport is a public airport serving the city of Myitkyina in northern Myanmar’s Kachin State, providing regional domestic flights and access to this remote 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_69d7bdf1fcd081909ffb0e0d6fa3a07d completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96bd75f508190aaae0969f33d1523 completed April 10, 2026, 9:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69f68eb5f4188190a5d014bf68557a96 completed May 2, 2026, 11:54 p.m.
Created at: April 9, 2026, 5:27 p.m.