Triple
T12697058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kishangarh Airport, Ajmer |
E303360
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Pushkar |
E272611
|
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: Pushkar | Statement: [Kishangarh Airport, Ajmer, near, Pushkar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pushkar Context triple: [Kishangarh Airport, Ajmer, near, Pushkar]
-
A.
Pushkar
chosen
Pushkar is a historic pilgrimage town in Rajasthan, India, famed for its sacred lake, Brahma temple, and vibrant annual camel and livestock fair.
-
B.
Jetpur
Jetpur is a textile and dyeing hub town in Gujarat, India, known for its cotton saree printing and screen-printing industries.
-
C.
Umarkhed
Umarkhed is a town in the Yavatmal district of Maharashtra, India, known as a local commercial and administrative center for the surrounding rural region.
-
D.
Jwalapur
Jwalapur is a prominent suburban town and commercial hub near Haridwar in the Indian state of Uttarakhand.
-
E.
Nagaur
Nagaur is a historic city in Rajasthan, India, known for its medieval fort, cultural heritage, and role as an important center in the Marwar region.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ed26588190ae76ff17159e06ec |
completed | April 10, 2026, 8:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f671b066348190aedfe186fc4724f9 |
completed | May 2, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:22 p.m.