Triple
T11875884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Churu district |
E282525
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Rajgarh |
E931720
|
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: Rajgarh | Statement: [Churu district, hasTown, Rajgarh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rajgarh Context triple: [Churu district, hasTown, Rajgarh]
-
A.
Rajgarh
Rajgarh is a town and administrative district headquarters in the central Indian state of Madhya Pradesh, known for its agricultural economy and historical temples.
-
B.
Rajgarh
chosen
Rajgarh is a town in the Indian state of Rajasthan, known as one of the settlements within the Alwar district.
-
C.
Ramgarh
Ramgarh is a town and administrative district headquarters in the Indian state of Jharkhand, known for its coal mining and industrial activities.
-
D.
Ramgarh
Ramgarh is a town in the Alwar district of Rajasthan, India, known for its historic forts, temples, and traditional Rajasthani culture.
-
E.
Ratangarh
Ratangarh is a town in the Churu district of Rajasthan, India, known for its historic 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8be1a22448190bd0722188c14d7bd |
completed | April 10, 2026, 9:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f64b7e6f0c8190b9df17f969df0deb |
completed | May 2, 2026, 7:07 p.m. |
Created at: April 8, 2026, 9:44 p.m.