Triple
T26641077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ยี่เป็ง |
E668779
|
entity |
| Predicate | มีรากทางวัฒนธรรมจาก |
P112778
|
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.
hasCulturalRoots
chosen
Indicates that something originates from, is shaped by, or is deeply connected to particular cultural traditions, practices, or heritage.
-
B.
hasCulturalRoute
Indicates that one entity is connected to another by a designated cultural route, such as a path, itinerary, or network highlighting cultural heritage or traditions.
-
C.
originatedInCulturalContext
Indicates that something began, developed, or was created within a particular cultural setting, tradition, or milieu.
-
D.
hasAssociatedCulture
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
E.
basedInCulture
Indicates that an entity is situated within, originates from, or is fundamentally associated with a particular culture.
- 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.