Triple
T24277953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thai Buddhists |
E605461
|
entity |
| Predicate | worshipAt |
P14925
|
FINISHED |
| Object | wat (Thai Buddhist temple) |
—
|
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: wat (Thai Buddhist temple) | Statement: [Thai Buddhists, worshipAt, wat (Thai Buddhist temple)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipAt Context triple: [Thai Buddhists, worshipAt, wat (Thai Buddhist temple)]
-
A.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
B.
worshipCenter
chosen
Indicates that one entity serves as a place or facility where another entity engages in religious worship or related spiritual activities.
-
C.
worshipPeak
Indicates a relationship where an entity directs religious or spiritual reverence, devotion, or worship toward a particular peak or mountain.
-
D.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
E.
worshipArea
Indicates a spatial or locational relationship where an area is designated or used for worship or religious practices.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d60a454819093b46556966640ab |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.