Triple
T18400093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushkar Lake |
E449968
|
entity |
| Predicate | hasGhat |
P13904
|
FINISHED |
| Object | Gau Ghat |
—
|
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: Gau Ghat | Statement: [Pushkar Lake, hasGhat, Gau Ghat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gau Ghat Context triple: [Pushkar Lake, hasGhat, Gau Ghat]
-
A.
Gau Ghat
chosen
Gau Ghat is a prominent riverside bathing and cremation ghat in the holy town of Pushkar, Rajasthan, revered by Hindu pilgrims for its religious rituals and ceremonies.
-
B.
Chir Ghat
Chir Ghat is a revered pilgrimage site in the Vraja region associated with Krishna’s playful pastimes on the banks of the Yamuna River.
-
C.
Guptar Ghat
Guptar Ghat is a sacred riverfront site in Ayodhya associated with Hindu religious traditions and pilgrimage along the banks of the Sarayu River.
-
D.
Keshi Ghat
Keshi Ghat is a historic riverside bathing ghat in Vrindavan on the banks of the Yamuna, revered in Hindu tradition for its association with Lord Krishna.
-
E.
Sita Ghat
Sita Ghat is a riverside pilgrimage spot in Bithoor, Uttar Pradesh, associated with Hindu religious traditions and local legends about Sita from the Ramayana.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e5194f2a8c8190afcd7db23e3795fb |
completed | April 19, 2026, 6:05 p.m. |
Created at: April 10, 2026, 10:46 a.m.