Triple
T20976405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanyakumari Temple |
E516636
|
entity |
| Predicate | devoteeType |
P141482
|
FINISHED |
| Object | Hindu pilgrims |
—
|
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: Hindu pilgrims | Statement: [Kanyakumari Temple, devoteeType, Hindu pilgrims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devoteeType Context triple: [Kanyakumari Temple, devoteeType, Hindu pilgrims]
-
A.
hasDevoteeType
chosen
Indicates that an entity has a devotee characterized by a specific type or category of devotion.
-
B.
devotionPracticedBy
Indicates that a particular form of devotion, worship, or religious practice is performed or carried out by a specified agent or practitioner.
-
C.
devoteesSeek
Indicates that devoted followers actively seek out, pursue, or strive to approach the object of their devotion.
-
D.
devoteeExpectation
Indicates that one party holds a belief or anticipation about how a devoted follower or admirer should think, feel, or behave in relation to someone or something.
-
E.
roleInGaudiyaVaishnavism
Indicates the specific function, position, or significance an entity holds within the theological, devotional, or institutional framework of Gaudiya Vaishnavism.
- 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba3df2081908c1db5f8610ba43d |
completed | April 21, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:47 p.m.