Triple
T8940910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rangaji Temple |
E212896
|
entity |
| Predicate | mainDeityForm |
P86454
|
FINISHED |
| Object | reclining form of Vishnu |
—
|
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: reclining form of Vishnu | Statement: [Rangaji Temple, mainDeityForm, reclining form of Vishnu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDeityForm Context triple: [Rangaji Temple, mainDeityForm, reclining form of Vishnu]
-
A.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
B.
deityCategory
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
C.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
D.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
E.
servedDeity
Indicates that one entity acted in service, devotion, or worship toward a particular deity.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66b8b37c8190bce6e049de8cf732 |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc60e0d7208190966797ce5f95fe49 |
completed | April 1, 2026, 12:03 a.m. |
Created at: March 30, 2026, 6:58 p.m.