Triple
T22562820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chhota Udaipur State |
E557860
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Rajpipla 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: Rajpipla State | Statement: [Chhota Udaipur State, borderedBy, Rajpipla State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rajpipla State Context triple: [Chhota Udaipur State, borderedBy, Rajpipla State]
-
A.
Rajpipla State
chosen
Rajpipla State was a former princely state in British India, located in present-day Gujarat.
-
B.
Bijawar State
Bijawar State was a former princely state in British India, located in the Bundelkhand region of present-day Madhya Pradesh.
-
C.
Mundhar State
Mundhar State was a small princely hill state located in the Simla Hills region of colonial India.
-
D.
Baraundha State
Baraundha State was a former princely state in British India located in the Bagelkhand region, ruled by local royalty under indirect colonial administration.
-
E.
Ali Rajpur State
Ali Rajpur State was a former princely state in British India, historically administered under the Rewa Kantha Agency in what is now western India.
- 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15fa7a828819096804ac928e2aaf9 |
completed | April 29, 2026, 1:32 a.m. |
Created at: April 16, 2026, 8:52 p.m.