Triple
T35320005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phra Bang Buddha image |
E1020010
|
entity |
| Predicate | currentShrine |
P27875
|
FINISHED |
| Object | Haw Pha Bang temple |
—
|
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: Haw Pha Bang temple | Statement: [Phra Bang Buddha image, currentShrine, Haw Pha Bang temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentShrine Context triple: [Phra Bang Buddha image, currentShrine, Haw Pha Bang temple]
-
A.
hasNearbyShrine
Indicates that one entity is located close to or in the vicinity of a shrine associated with another entity.
-
B.
containsShrine
Indicates that one entity includes or has within its boundaries a shrine associated with it.
-
C.
stateShrineOf
Indicates that one entity is officially designated as a state-recognized shrine associated with or located within another entity (typically a state or region).
-
D.
associatedShrine
chosen
Indicates that there is a specific shrine linked or connected to the given entity, typically as its dedicated or related place of worship or reverence.
-
E.
placeOfShrine
Indicates the location where a shrine is situated or established.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: May 3, 2026, 4:03 p.m.