Triple
T3531019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadoti |
E74659
|
entity |
| Predicate | hasHistoricCity |
P3786
|
FINISHED |
| Object | Jhalawar |
E364482
|
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: Jhalawar | Statement: [Hadoti, hasHistoricCity, Jhalawar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jhalawar Context triple: [Hadoti, hasHistoricCity, Jhalawar]
-
A.
Jhalawar
chosen
Jhalawar is a town and administrative district headquarters in southeastern Rajasthan, India, known for its historic forts, temples, and rich Hadoti cultural heritage.
-
B.
Ramgarh
Ramgarh is a town and administrative district headquarters in the Indian state of Jharkhand, known for its coal mining and industrial activities.
-
C.
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.
-
D.
Jhabua
Jhabua is a town and administrative district headquarters in western Madhya Pradesh, India, known for its significant tribal population and culture.
-
E.
Rajpura
Rajpura is an industrial and commercial town in the Patiala district of Punjab, India, known for its manufacturing base and strategic location as a transport hub.
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc988ee081909c6b9d5eed0d2d6d |
completed | March 8, 2026, 6:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b44eeb831481909f9def02fe995c69 |
completed | March 13, 2026, 5:52 p.m. |
Created at: March 8, 2026, 3:19 p.m.