Triple
T13865227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagaur Fort |
E333303
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Nagaur |
E333303
|
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: Nagaur | Statement: [Nagaur Fort, locatedIn, Nagaur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nagaur Context triple: [Nagaur Fort, locatedIn, Nagaur]
-
A.
Nagaur
chosen
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.
-
B.
Nawalgarh
Nawalgarh is a historic town in Rajasthan, India, renowned for its richly painted havelis and cultural heritage within the Shekhawati region.
-
C.
Kishangarh
Kishangarh is a town and legislative assembly constituency in Rajasthan, India, known for its marble industry and distinctive miniature paintings.
-
D.
Nakodar
Nakodar is a prominent town in the Indian state of Punjab, known for its historical significance and cultural heritage within the Jalandhar region.
-
E.
Laxmangarh
Laxmangarh is a town in the Sikar district of Rajasthan, India, known for its historic fort, havelis, and traditional Rajasthani architecture.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de05c30d9c81908217d41a3b4aaf85 |
completed | April 14, 2026, 9:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd192b5e508190b2d385657f9e358f |
completed | May 7, 2026, 10:58 p.m. |
Created at: April 9, 2026, 10:14 p.m.