Triple
T21217650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palanpur Agency |
E522877
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Cutch 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: Cutch State | Statement: [Palanpur Agency, borderedBy, Cutch State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cutch State Context triple: [Palanpur Agency, borderedBy, Cutch State]
-
A.
Cutch State
chosen
Cutch State was a princely state in western India, centered in the Kutch (Kachchh) region of present-day Gujarat and ruled historically by the Jadeja Rajput dynasty.
-
B.
Morvi State
Morvi State was a former princely state in western India, historically governed by the Jadeja Rajput dynasty.
-
C.
Bijawar State
Bijawar State was a former princely state in British India, located in the Bundelkhand region of present-day Madhya Pradesh.
-
D.
Mundhar State
Mundhar State was a small princely hill state located in the Simla Hills region of colonial India.
-
E.
Dhar State
Dhar State was a former princely state in central India, historically ruled by the Pawar (Parmar) Maratha dynasty with its capital at the town of Dhar.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7347613308190a1c9f4ea51591d4b |
completed | April 21, 2026, 8:25 a.m. |
Created at: April 16, 2026, 3:42 p.m.