Triple
T35902677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wat Si Chum |
E1038393
|
entity |
| Predicate | buddhaImagePosture |
P141233
|
FINISHED |
| Object | subduing Mara posture |
—
|
NE NERFINISHED |
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: subduing Mara posture | Statement: [Wat Si Chum, buddhaImagePosture, subduing Mara posture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buddhaImagePosture Context triple: [Wat Si Chum, buddhaImagePosture, subduing Mara posture]
-
A.
recliningBuddhaPosition
Indicates that an entity is positioned in the characteristic lying-down posture associated with a reclining Buddha.
-
B.
viewOnBuddha
Indicates that an entity holds a particular perspective, opinion, or interpretive stance regarding Buddha.
-
C.
hasDeityPosture
chosen
Indicates the specific physical stance or pose attributed to a deity in a given context.
-
D.
typicalMudra
Indicates that one entity is the characteristic or commonly used mudra (hand gesture) associated with another entity, such as a deity, practice, or tradition.
-
E.
statusInBuddhism
Indicates the recognized role, standing, or significance an entity holds within Buddhist doctrine, practice, or community.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.