Triple
T20716567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulagalantha Perumal Temple |
E509184
|
entity |
| Predicate | hasDeityPosture |
P141233
|
FINISHED |
| Object | standing posture |
—
|
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: standing posture | Statement: [Ulagalantha Perumal Temple, hasDeityPosture, standing posture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeityPosture Context triple: [Ulagalantha Perumal Temple, hasDeityPosture, standing posture]
-
A.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
B.
hasDeityAspect
Indicates that one entity embodies, represents, or functions as a specific divine aspect or manifestation of another deity.
-
C.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
D.
hasDeities
Indicates that one entity possesses, is associated with, or is served by one or more deities.
-
E.
portraysDeity
Indicates that one entity represents, depicts, or characterizes another entity as a deity or divine being.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:16 p.m.