Triple
T11377734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maheshwar |
E269512
|
entity |
| Predicate | wasCapitalOf |
P3417
|
FINISHED |
| Object | Holkar State |
E296940
|
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: Holkar State | Statement: [Maheshwar, wasCapitalOf, Holkar State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Holkar State Context triple: [Maheshwar, wasCapitalOf, Holkar State]
-
A.
Holkar State of Indore
chosen
Holkar State of Indore was a prominent Maratha-ruled princely state in central India, centered on the city of Indore and historically governed by the Holkar dynasty.
-
B.
Holkar
Holkar refers to a prominent Maratha dynasty that ruled the Indore State in central India and played a significant role in 18th- and 19th-century Indian politics.
-
C.
Jahangir Nagar
Jahangir Nagar is the former Mughal-era name of present-day Dhaka, given in honor of the emperor Jahangir.
-
D.
Shahpura State
Shahpura State was a princely state in British India, located in the Rajputana region (now in Rajasthan) and ruled by Rajput nobility.
-
E.
Suratgarh
Suratgarh is a town in the northern Indian state of Rajasthan, known for its agricultural significance and military and air force establishments.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7fc30f5d48190bb273df4c9e583a9 |
completed | April 9, 2026, 7:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e55697b2388190929d7e0b15d809ba |
completed | April 19, 2026, 10:26 p.m. |
Created at: April 8, 2026, 9:33 p.m.