Triple
T8760404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bharatpur State |
E208181
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Alwar State |
E205377
|
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: Alwar State | Statement: [Bharatpur State, borderedBy, Alwar State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alwar State Context triple: [Bharatpur State, borderedBy, Alwar State]
-
A.
Alwar State
chosen
Alwar State was a princely state in northern India, ruled by Rajput princes and later integrated into the modern state of Rajasthan after Indian independence.
-
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.
Patdi State
Patdi State was a former princely state in western India historically governed by the Rajput Jhala dynasty.
-
D.
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.
-
E.
Rajpipla State
Rajpipla State was a former princely state in British India, located in present-day Gujarat.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5df9729481908679151988b76d2f |
completed | March 31, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf434bcac08190be07175a26804185 |
completed | April 3, 2026, 4:34 a.m. |
Created at: March 30, 2026, 6:40 p.m.