Triple
T26641055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ยี่เป็ง |
E668779
|
entity |
| Predicate | จัดขึ้นในภูมิภาค |
P84795
|
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.
takesPlaceInRegion
chosen
Indicates that an event or occurrence happens within the boundaries of a specified geographic or administrative region.
-
B.
compiledInRegion
Indicates that a software artifact was compiled within a specific geographic or logical region.
-
C.
расположена в части страны
Indicates that one place or area is situated within a specific part or region of a country.
-
D.
tookPlaceInAdministrativeEntity
Indicates that an event or occurrence happened within the jurisdiction or boundaries of a specific administrative entity.
-
E.
typicallyHeldIn
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
- 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.