Triple

T37846185
Position Surface form Disambiguated ID Type / Status
Subject Mandalay International Airport E943606 entity
Predicate alternativeName P39 FINISHED
Object Tada-U Airport
Tada-U Airport is the main international airport serving Mandalay, Myanmar, functioning as a key aviation hub in the central part of the country.
E2254895 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: Tada-U Airport | Statement: [Mandalay International Airport, alternativeName, Tada-U Airport]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Tada-U Airport
Triple: [Mandalay International Airport, alternativeName, Tada-U Airport]
Generated description
Tada-U Airport is the main international airport serving Mandalay, Myanmar, functioning as a key aviation hub in the central part of the country.

Provenance (5 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_69f76eeb0f7081908d6d3adbc469889c completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbb21fbef4819089f0cebd9b43ce96 completed May 6, 2026, 9:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a415d1a62088190a5dee6dfd8338b37 completed June 28, 2026, 5:42 p.m.
NEDg Description generation batch_6a415e84111481908fe45f196ab6ee26 completed June 28, 2026, 5:48 p.m.
NED2 Entity disambiguation (via description) batch_6a415f782d9881909ed47dd8690ce40f completed June 28, 2026, 5:52 p.m.
Created at: May 3, 2026, 4:19 p.m.