Triple
T26641087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ยี่เป็ง |
E668779
|
entity |
| Predicate | มีสถานที่จัดสำคัญ |
P147149
|
FINISHED |
| Object | วัดในจังหวัดเชียงใหม่ |
—
|
LITERAL 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: วัดในจังหวัดเชียงใหม่ | Statement: [ยี่เป็ง, มีสถานที่จัดสำคัญ, วัดในจังหวัดเชียงใหม่]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: มีสถานที่จัดสำคัญ Context triple: [ยี่เป็ง, มีสถานที่จัดสำคัญ, วัดในจังหวัดเชียงใหม่]
-
A.
significantEventPlace
Indicates the place where a significant event occurred or is associated with an entity.
-
B.
importantJunctionTown
Indicates that a town functions as a key junction point where major routes, lines, or pathways intersect or connect.
-
C.
hasFestivalImportance
Indicates that something holds notable significance, relevance, or prominence within the context of a festival or festive event.
-
D.
importantSaint
Indicates that the subject is recognized as a particularly significant or highly revered saint within a religious or spiritual tradition.
-
E.
locationOfEventOrganized
chosen
Indicates the place where a particular organized event is held or takes place.
- F. None of above.
Provenance (3 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f616320b9c8190b3a5792ffcfe3bc1 |
completed | May 2, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:29 a.m.