Triple
T35902682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wat Si Chum |
E1038393
|
entity |
| Predicate | mandapaFeature |
P166281
|
FINISHED |
| Object | high enclosing walls |
—
|
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: high enclosing walls | Statement: [Wat Si Chum, mandapaFeature, high enclosing walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mandapaFeature Context triple: [Wat Si Chum, mandapaFeature, high enclosing walls]
-
A.
hasMandapa
Indicates that a structure (typically a temple) includes or is associated with a mandapa, an attached or nearby pillared hall or pavilion used for rituals or gatherings.
-
B.
AayiramKaalMandapamPillarCountApprox
Indicates an approximate count of the pillars in the Aayiram Kaal Mandapam.
-
C.
gopuramStyle
Indicates that something is characterized by or constructed in the architectural style associated with a gopuram (a monumental temple gateway tower).
-
D.
templeComplexFeature
chosen
Indicates that one entity is a structural or functional feature that forms part of a larger temple complex.
-
E.
typicalShrineFeature
Indicates that something is a characteristic or commonly found element of a shrine.
- 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_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.