Triple
T25555119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paramekkavu Bhagavathy Temple |
E640546
|
entity |
| Predicate | hasDevoteeCommunity |
P169214
|
FINISHED |
| Object | Hindu devotees in Kerala |
—
|
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 devotees in Kerala | Statement: [Paramekkavu Bhagavathy Temple, hasDevoteeCommunity, Hindu devotees in Kerala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevoteeCommunity Context triple: [Paramekkavu Bhagavathy Temple, hasDevoteeCommunity, Hindu devotees in Kerala]
-
A.
hasDevoteeType
Indicates that an entity has a devotee characterized by a specific type or category of devotion.
-
B.
receivesDevoteesFrom
Indicates that an entity (such as a place, person, or institution) is the destination to which devotees come or are directed from another entity.
-
C.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
D.
hasParishCommunity
Indicates that an entity is associated with, served by, or belongs to a specific parish community.
-
E.
devoteesSeek
Indicates that devoted followers actively seek out, pursue, or strive to approach the object of their devotion.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 21, 2026, 3:39 p.m.