Triple
T13356719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumaoni people |
E318710
|
entity |
| Predicate | localDeity |
P51997
|
FINISHED |
| Object | Bholanath |
E163410
|
NE 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: Bholanath | Statement: [Kumaoni people, localDeity, Bholanath]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bholanath Context triple: [Kumaoni people, localDeity, Bholanath]
-
A.
Bholenath
chosen
Bholenath is a beloved epithet of the Hindu god Shiva, emphasizing his innocent, benevolent, and easily-pleased nature as a divine protector of devotees.
-
B.
Bholath
Bholath is a small town in the Kapurthala district of the Indian state of Punjab, known primarily as a local administrative and market center for surrounding rural areas.
-
C.
Gopala
Gopala is a pastoral form of the Hindu god Krishna, revered especially as a divine cowherd and protector of cows.
-
D.
Taraknath
Taraknath is an Indian given name commonly used for males, often associated with Bengali cultural and religious traditions.
-
E.
Raghunath
Raghunath is a male given name commonly used in India, often associated with Hindu cultural and religious traditions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae47e99081909d8b5dba97a11988 |
completed | April 12, 2026, 2:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f72677b2a48190aad30f3ee6cacefb |
completed | May 3, 2026, 10:41 a.m. |
Created at: April 9, 2026, 9:32 p.m.