Triple
T20594919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jhabua State |
E506025
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Jhabua |
—
|
NE NERFINISHED |
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: Jhabua | Statement: [Jhabua State, capital, Jhabua]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jhabua Context triple: [Jhabua State, capital, Jhabua]
-
A.
Jhabua
chosen
Jhabua is a town and administrative district headquarters in western Madhya Pradesh, India, known for its significant tribal population and culture.
-
B.
Jambusar
Jambusar is a town in the Bharuch district of Gujarat, India, known for its historical significance and regional trade and agriculture.
-
C.
Bhopalgarh
Bhopalgarh is a town in the Indian state of Rajasthan, known for its rural setting and administrative role within the region.
-
D.
Dabhoi
Dabhoi is a historic town in the Indian state of Gujarat, known for its ancient fortifications and architectural heritage.
-
E.
Alirajpur
Alirajpur is a town and district headquarters in western Madhya Pradesh, India, known for its predominantly tribal population and vibrant indigenous culture.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1b1c6c8190a2d85e7a390fc6a5 |
completed | April 20, 2026, 10:35 p.m. |
Created at: April 16, 2026, 11:40 a.m.