Triple
T22248604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasol |
E549911
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Manikaran |
—
|
NE NERFINISHED |
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: Manikaran | Statement: [Kasol, near, Manikaran]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Manikaran Context triple: [Kasol, near, Manikaran]
-
A.
Manikaran
chosen
Manikaran is a small pilgrimage town in Himachal Pradesh, India, renowned for its hot springs and Sikh and Hindu religious sites in the Parvati Valley.
-
B.
Manjai Kunda
Manjai Kunda is a residential neighborhood within the urban area of Serekunda in The Gambia.
-
C.
Daksiri
Daksiri is a principal settlement and local center of the Kilba people in northeastern Nigeria.
-
D.
Sautramani
Sautramani is a specialized Vedic sacrificial ritual associated with Indra and Soma, performed to atone for ritual errors and restore cosmic and social order.
-
E.
Bhailsa
Bhailsa is the former historical name of Vidisha, an ancient city in the central Indian state of Madhya Pradesh known for its rich archaeological and cultural heritage.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f13219dc3481908dd987c4e98623e6 |
completed | April 28, 2026, 10:18 p.m. |
Created at: April 16, 2026, 8:38 p.m.