Triple

T27097025
Position Surface form Disambiguated ID Type / Status
Subject Xinjiang Airport Group E686331 entity
Predicate operatesAirport P38515 FINISHED
Object Tazhong Airport
Tazhong Airport is a regional civil airport located in the Xinjiang Uyghur Autonomous Region of China, serving the remote Tazhong area in the Taklamakan Desert.
E1785254 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: Tazhong Airport | Statement: [Xinjiang Airport Group, operatesAirport, Tazhong 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: Tazhong Airport
Triple: [Xinjiang Airport Group, operatesAirport, Tazhong Airport]
Generated description
Tazhong Airport is a regional civil airport located in the Xinjiang Uyghur Autonomous Region of China, serving the remote Tazhong area in the Taklamakan Desert.

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_69ef1489f8b481908e24a1985982bd26 completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69f623b1d8b48190ae71d57f60d2e327 completed May 2, 2026, 4:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12e42f749c8190828b02fa6eba7229 completed May 24, 2026, 11:42 a.m.
NEDg Description generation batch_6a12e4da65dc8190801cafed5fb95685 completed May 24, 2026, 11:45 a.m.
NED2 Entity disambiguation (via description) batch_6a12e5acc5c8819081be9900ea407d65 completed May 24, 2026, 11:49 a.m.
Created at: April 27, 2026, 8:45 a.m.