Triple
T38313748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chitai Golu Devta Temple |
E1033766
|
entity |
| Predicate | devoteeOrigin |
P111925
|
FINISHED |
| Object | devotees from Uttarakhand |
—
|
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: devotees from Uttarakhand | Statement: [Chitai Golu Devta Temple, devoteeOrigin, devotees from Uttarakhand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devoteeOrigin Context triple: [Chitai Golu Devta Temple, devoteeOrigin, devotees from Uttarakhand]
-
A.
deityOrigin
Indicates that one entity is the source, creator, or originating cause of a deity or divine being.
-
B.
devoteesSeek
Indicates that devoted followers actively seek out, pursue, or strive to approach the object of their devotion.
-
C.
devotionPracticedBy
Indicates that a particular form of devotion, worship, or religious practice is performed or carried out by a specified agent or practitioner.
-
D.
devotionOriginatedInCentury
Indicates the century during which a particular devotion first originated or began.
-
E.
receivesDevoteesFrom
chosen
Indicates that an entity (such as a place, person, or institution) is the destination to which devotees come or are directed from another 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.