Triple
T10223050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jyotirlinga of Shiva at Trimbakeshwar |
E242629
|
entity |
| Predicate | hasPriestCommunity |
P79707
|
FINISHED |
| Object | Hindu Brahmin priests |
—
|
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 Brahmin priests | Statement: [Jyotirlinga of Shiva at Trimbakeshwar, hasPriestCommunity, Hindu Brahmin priests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPriestCommunity Context triple: [Jyotirlinga of Shiva at Trimbakeshwar, hasPriestCommunity, Hindu Brahmin priests]
-
A.
hasParishCommunity
Indicates that an entity is associated with, served by, or belongs to a specific parish community.
-
B.
hasMonasticCommunities
Indicates that an entity possesses, hosts, or is associated with one or more monastic communities.
-
C.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
D.
hasClergyLikeGroup
chosen
Indicates that an entity possesses or is associated with a group functioning in a clergy-like or religious-leadership role.
-
E.
hasCongregation
Indicates that an entity is associated with or serves as the gathering place or organized group of worshippers for a religious community.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa8305e481908ee1fc1d9eda6fa0 |
completed | April 6, 2026, 12:43 p.m. |
| PD | Predicate disambiguation | batch_69d3955f61f88190b8d37ff645cd44d3 |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11:10 a.m.