Triple

T35902700
Position Surface form Disambiguated ID Type / Status
Subject Wat Si Chum E1038393 entity
Predicate nearbySite P350 FINISHED
Object Wat Phra Phai Luang
Wat Phra Phai Luang is a historic temple complex in Sukhothai, Thailand, notable for its early Khmer-style architecture and important role in the region’s pre-Sukhothai period.
E2163837 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: Wat Phra Phai Luang | Statement: [Wat Si Chum, nearbySite, Wat Phra Phai Luang]
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: Wat Phra Phai Luang
Triple: [Wat Si Chum, nearbySite, Wat Phra Phai Luang]
Generated description
Wat Phra Phai Luang is a historic temple complex in Sukhothai, Thailand, notable for its early Khmer-style architecture and important role in the region’s pre-Sukhothai period.

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_69f76e2190f88190beb2eed798a4ef01 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7aa6b70948190a9f0b5f76c095d4e completed May 3, 2026, 8:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38b6f1e65c81909d9e2b85fb553ece completed June 22, 2026, 4:15 a.m.
NEDg Description generation batch_6a38b7d8c5fc8190a7cce91a93d1b905 completed June 22, 2026, 4:19 a.m.
NED2 Entity disambiguation (via description) batch_6a38b86a90b48190810a306e1cf50744 completed June 22, 2026, 4:22 a.m.
Created at: May 3, 2026, 4:07 p.m.