Triple
T2964011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marwar |
E80117
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Sirohi |
E216168
|
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: Sirohi | Statement: [Marwar, majorCity, Sirohi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sirohi Context triple: [Marwar, majorCity, Sirohi]
-
A.
Sirohi State
chosen
Sirohi State was a princely state in western India, ruled by Rajput chiefs and later integrated into the Indian Union after independence.
-
B.
Jalore
Jalore is a historic town and district headquarters in the Indian state of Rajasthan, known for its ancient fort and role in the Marwar region’s history.
-
C.
Banswara State
Banswara State was a princely state in what is now Rajasthan, India, historically ruled by Rajput chiefs and later integrated into the Indian Union after independence.
-
D.
Pratapgarh
Pratapgarh is a town in the Indian state of Rajasthan known for its historical association with the Mewar region and its distinctive tribal culture and handicrafts.
-
E.
Tikamgarh
Tikamgarh is a town and administrative center in central India, known for its historical forts and temples in the state of Madhya Pradesh.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9958b1e48190a77f37bf63333c5b |
completed | March 8, 2026, 3:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b261d8d40c8190b5f0a78e4d3069f6 |
completed | March 12, 2026, 6:48 a.m. |
Created at: March 8, 2026, 2:58 p.m.