Triple
T23485386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kate Festival |
E570519
|
entity |
| Predicate | mainRitualSite |
P90408
|
FINISHED |
| Object | Po Klong Garai Cham Towers |
—
|
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: Po Klong Garai Cham Towers | Statement: [Kate Festival, mainRitualSite, Po Klong Garai Cham Towers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRitualSite Context triple: [Kate Festival, mainRitualSite, Po Klong Garai Cham Towers]
-
A.
mainLocationOfRituals
chosen
Indicates that a place serves as the primary setting where a group's rituals are regularly performed.
-
B.
ritualCentersOn
Indicates that a ritual is primarily focused on, organized around, or thematically centered on a particular entity, object, or concept.
-
C.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing rituals or ceremonial practices.
-
D.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
E.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7538a8c8190b7effcc39a3f9787 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:03 p.m.