Triple
T12137364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guhila dynasty |
E289093
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Nagda |
E803624
|
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: Nagda | Statement: [Guhila dynasty, capital, Nagda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nagda Context triple: [Guhila dynasty, capital, Nagda]
-
A.
Nagda
chosen
Nagda is an industrial town in the Indian state of Madhya Pradesh, known especially for its large textile and chemical manufacturing units.
-
B.
Nawalgarh
Nawalgarh is a historic town in Rajasthan, India, renowned for its richly painted havelis and cultural heritage within the Shekhawati region.
-
C.
Jwalapur
Jwalapur is a prominent suburban town and commercial hub near Haridwar in the Indian state of Uttarakhand.
-
D.
Narnaund
Narnaund is a prominent town in the northern Indian state of Haryana, known for its agricultural economy and role as a local commercial hub.
-
E.
Rupnagar
Rupnagar is a historic town in the Indian state of Punjab, known as one of the earliest Indus Valley Civilization sites and an important regional administrative and cultural center.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9158dd00c819082651891898b91bb |
completed | April 10, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65556e718819092736cd89c326fb5 |
completed | May 2, 2026, 7:49 p.m. |
Created at: April 8, 2026, 9:49 p.m.