Triple
T20716582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulagalantha Perumal Temple |
E509184
|
entity |
| Predicate | hasSacredDirection |
P124196
|
FINISHED |
| Object | east entrance |
—
|
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: east entrance | Statement: [Ulagalantha Perumal Temple, hasSacredDirection, east entrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredDirection Context triple: [Ulagalantha Perumal Temple, hasSacredDirection, east entrance]
-
A.
sacredDirection
chosen
Indicates a directional relationship that is regarded as holy, spiritually significant, or ritually privileged within a religious or cultural context.
-
B.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
C.
hasSacredSpring
Indicates that one entity possesses, contains, or is associated with a spring regarded as sacred or holy.
-
D.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
E.
hasSacredNumber
Indicates that a particular number is regarded as sacred, holy, or spiritually significant in relation to an entity.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d1f3308190ae594a5b9e4ab9d5 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:16 p.m.