Triple
T27494145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phra Buddha Sihing |
E693976
|
entity |
| Predicate | claimedOriginalLocation |
P76139
|
FINISHED |
| Object | Wat Phra Singh, Chiang Mai |
—
|
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: Wat Phra Singh, Chiang Mai | Statement: [Phra Buddha Sihing, claimedOriginalLocation, Wat Phra Singh, Chiang Mai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedOriginalLocation Context triple: [Phra Buddha Sihing, claimedOriginalLocation, Wat Phra Singh, Chiang Mai]
-
A.
originalLocationStatus
Indicates the status or condition of an entity’s original location, such as whether it remains, has changed, or is otherwise affected.
-
B.
hasOriginalLocation
chosen
Indicates that an entity was initially located or situated at a specified place or position before any change or movement occurred.
-
C.
originalLocationType
Indicates the type or category of the place where something was originally located or came from.
-
D.
originalLocationEvent
Indicates that an event occurred at or is associated with the place where an entity was originally located or originated.
-
E.
reportedLocation
Indicates that an entity has been specified or recorded as being at a particular location, typically based on a report or observation rather than direct verification.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 1:07 p.m.