Triple

T30060416
Position Surface form Disambiguated ID Type / Status
Subject Thọ Xuan Airport E763861 entity
Predicate formerlyKnownAs P65 FINISHED
Object Sao Vàng Airport
Sao Vàng Airport is a Vietnamese airport in Thanh Hóa Province that now operates under the name Thọ Xuân Airport, serving both military and civilian flights.
E1901544 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: Sao Vàng Airport | Statement: [Thọ Xuan Airport, formerlyKnownAs, Sao Vàng 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: Sao Vàng Airport
Triple: [Thọ Xuan Airport, formerlyKnownAs, Sao Vàng Airport]
Generated description
Sao Vàng Airport is a Vietnamese airport in Thanh Hóa Province that now operates under the name Thọ Xuân Airport, serving both military and civilian flights.

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_69f224716378819087a722e487832b70 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67ca34d4081909ea4b2b02523d46a completed May 2, 2026, 10:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a274c9c5bd48190ad27234fe778e779 completed June 8, 2026, 11:13 p.m.
NEDg Description generation batch_6a274dcada9c8190bed32d44fabd85df completed June 8, 2026, 11:18 p.m.
NED2 Entity disambiguation (via description) batch_6a274e8893b88190b281e021f785daa7 completed June 8, 2026, 11:21 p.m.
Created at: April 29, 2026, 6:57 p.m.