Triple
T26641065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ยี่เป็ง |
E668779
|
entity |
| Predicate | มีพิธีกรรมสำคัญ |
P129522
|
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.
hasCeremonies
chosen
Indicates that an entity conducts, includes, or is associated with one or more formal ceremonies or ritual events.
-
B.
主な神事
Indicates the primary or main Shinto ritual(s) associated with something (such as a shrine, festival, or deity).
-
C.
ceremonySignificance
Indicates the importance, meaning, or role that a particular ceremony holds within a given context or for specific participants.
-
D.
ceremonialAction
Indicates an action performed as part of a formal ceremony or ritual, typically following prescribed traditions or symbolic procedures.
-
E.
ritualEvent
Indicates that an event is a ritual or ceremonial occurrence, typically involving prescribed actions, symbols, or practices performed according to tradition or custom.
- 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_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 2:29 a.m.