Triple
T5061104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vijay Ghat |
E114022
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Kisan Ghat |
E24554
|
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: Kisan Ghat | Statement: [Vijay Ghat, near, Kisan Ghat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kisan Ghat Context triple: [Vijay Ghat, near, Kisan Ghat]
-
A.
Kisan Ghat
chosen
Kisan Ghat is a memorial in Delhi dedicated to Indian farmers, located near the Raj Ghat complex.
-
B.
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.
-
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.
Gomti Ghat
Gomti Ghat is a revered riverfront pilgrimage spot in Dwarka, Gujarat, where devotees perform holy rituals and bathe in the Gomti River before visiting nearby temples.
-
E.
Kaliya Ghat
Kaliya Ghat is a sacred riverbank site in Vrindavan associated with the Hindu legend of Lord Krishna subduing the serpent Kaliya in the Yamuna River.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74740ae08190930f1fd57187334e |
completed | March 20, 2026, 4:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69beb102bb348190b235e4adb7a3f88b |
completed | March 21, 2026, 2:53 p.m. |
Created at: March 20, 2026, 1:38 p.m.