Triple
T20500426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alirajpur State |
E503284
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Jhabua State |
—
|
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 State | Statement: [Alirajpur State, hasBorderWith, Jhabua State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jhabua State Context triple: [Alirajpur State, hasBorderWith, Jhabua State]
-
A.
Jhabua State
chosen
Jhabua State was a former princely state in western India, located in what is now Madhya Pradesh and historically ruled by Rajput chiefs under British suzerainty.
-
B.
Alirajpur State
Alirajpur State was a former princely state in colonial India, located in what is now Madhya Pradesh and ruled by local Rajput chiefs under British suzerainty.
-
C.
Mundhar State
Mundhar State was a small princely hill state located in the Simla Hills region of colonial India.
-
D.
Narsinghgarh State
Narsinghgarh State was a former princely state in central India, historically ruled by local royalty under British suzerainty.
-
E.
Dhrol State
Dhrol State was a former princely state in western India historically governed by the Jadeja Rajput dynasty.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cc10cd08190915b6c29c6473f77 |
completed | April 20, 2026, 9:38 p.m. |
Created at: April 16, 2026, 11:35 a.m.