Triple

T26743365
Position Surface form Disambiguated ID Type / Status
Subject Phitsanulok E674325 entity
Predicate hasAirport P105 FINISHED
Object Phitsanulok Airport
Phitsanulok Airport is a regional public airport in northern Thailand that serves the city of Phitsanulok and its surrounding provinces with domestic flights.
E1759000 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: Phitsanulok Airport | Statement: [Phitsanulok, hasAirport, Phitsanulok 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: Phitsanulok Airport
Triple: [Phitsanulok, hasAirport, Phitsanulok Airport]
Generated description
Phitsanulok Airport is a regional public airport in northern Thailand that serves the city of Phitsanulok and its surrounding provinces with domestic 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_69eecda63a3881908095c47900692e65 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f61880cac881909ed6b653b09164d2 completed May 2, 2026, 3:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12535d778081909038f101f94fd48b completed May 24, 2026, 1:24 a.m.
NEDg Description generation batch_6a1253ea3fdc8190a7aa04fd8e904209 completed May 24, 2026, 1:27 a.m.
NED2 Entity disambiguation (via description) batch_6a1254cce7dc8190aaf86de7f09fba53 completed May 24, 2026, 1:30 a.m.
Created at: April 27, 2026, 3:50 a.m.