Triple
T11451245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajan Bund |
E271399
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Bharatpur city |
E62480
|
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: Bharatpur city | Statement: [Ajan Bund, near, Bharatpur city]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bharatpur city Context triple: [Ajan Bund, near, Bharatpur city]
-
A.
Bharatpur
chosen
Bharatpur is a historic city in eastern Rajasthan, India, known for the Keoladeo National Park, a UNESCO World Heritage-listed bird sanctuary.
-
B.
Udaipur
Udaipur is a historic city in India renowned for its lakes, palaces, and role as a former capital of the Mewar kingdom.
-
C.
Udaipur
Udaipur is a historic town in the Indian state of Tripura, known for its ancient temples and scenic lakes.
-
D.
Udaipur
Udaipur is a town in the Lahaul and Spiti district of Himachal Pradesh, India, known for its scenic Himalayan setting and the ancient Mrikula Devi Temple.
-
E.
Sawai Madhopur
Sawai Madhopur is a town in Rajasthan, India, best known as the main gateway to the tiger-rich Ranthambore region and its historic fort.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d81c6f4d788190ac59b0df946cebbc |
completed | April 9, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6040733648190a10f9553b3ac87a7 |
completed | April 20, 2026, 10:46 a.m. |
Created at: April 8, 2026, 9:35 p.m.