Triple
T2640370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mewar |
E62850
|
entity |
| Predicate | historicalCapital |
P2536
|
FINISHED |
| Object | Chittorgarh |
E288897
|
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: Chittorgarh | Statement: [Mewar, historicalCapital, Chittorgarh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chittorgarh Context triple: [Mewar, historicalCapital, Chittorgarh]
-
A.
Chittorgarh
chosen
Chittorgarh is a historic city in Rajasthan, India, renowned for its massive hilltop fort, tales of Rajput valor, and rich cultural traditions.
-
B.
Chanderi
Chanderi is a historic town in central India renowned for its medieval architecture and its traditional handwoven Chanderi silk and cotton textiles.
-
C.
Marwar
Marwar is a historic desert region in the western part of Rajasthan, India, known for its Rajput heritage, forts, and distinctive Marwari culture and language.
-
D.
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.
-
E.
Udaipur
Udaipur is a historic city in India renowned for its lakes, palaces, and role as a former capital of the Mewar kingdom.
- 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_69ab4c3f2dcc819082df80f5e032f690 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abd8fc8ee881908a9f6820d8934a62 |
completed | March 7, 2026, 7:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afb672731881909f7df113a279e1a5 |
completed | March 10, 2026, 6:13 a.m. |
Created at: March 6, 2026, 9:53 p.m.