Triple
T9683964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jhalawar State |
E234357
|
entity |
| Predicate | capital |
P234
|
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: [Jhalawar State, capital, Jhalawar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jhalawar Context triple: [Jhalawar State, capital, 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.
Karauli
Karauli is a historic town and pilgrimage center in the Indian state of Rajasthan, known for its ancient temples and distinctive red sandstone architecture.
-
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.
Chandanpura
Chandanpura is a locality in Chittagong, Bangladesh, known for its historic architecture and urban commercial activity.
-
E.
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.
- 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ccf21a08190a1302b933b9e50be |
completed | April 1, 2026, 10:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2284e9d0c8190ab09ad1fd0a123e3 |
completed | April 5, 2026, 9:15 a.m. |
Created at: March 30, 2026, 8:16 p.m.