Triple

T27021222
Position Surface form Disambiguated ID Type / Status
Subject Phop Phra District E680667 entity
Predicate hasAdministrativeCenter P1474 FINISHED
Object Phop Phra
Phop Phra is a town in Tak Province, western Thailand, serving as the local administrative and service hub for the surrounding rural district near the Myanmar border.
E1757446 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: Phop Phra | Statement: [Phop Phra District, hasAdministrativeCenter, Phop Phra]
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: Phop Phra
Triple: [Phop Phra District, hasAdministrativeCenter, Phop Phra]
Generated description
Phop Phra is a town in Tak Province, western Thailand, serving as the local administrative and service hub for the surrounding rural district near the Myanmar border.

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_69eeeb5450988190bfc9a3c012ac463a completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f622048e10819094ea97b9c638de15 completed May 2, 2026, 4:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1247f17cf081908cecc8a7bcef84d2 completed May 24, 2026, 12:36 a.m.
NEDg Description generation batch_6a1248bb58a48190ae84e7b538b10503 completed May 24, 2026, 12:39 a.m.
NED2 Entity disambiguation (via description) batch_6a124973e3c88190898b0cece69419b3 completed May 24, 2026, 12:42 a.m.
Created at: April 27, 2026, 7:08 a.m.