Triple
T22859585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rewa Kantha |
E566876
|
entity |
| Predicate | includedPrincelyState |
P74995
|
FINISHED |
| Object | Ali Rajpur 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: Ali Rajpur State | Statement: [Rewa Kantha, includedPrincelyState, Ali Rajpur State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ali Rajpur State Context triple: [Rewa Kantha, includedPrincelyState, Ali Rajpur State]
-
A.
Ali Rajpur State
chosen
Ali Rajpur State was a former princely state in British India, historically administered under the Rewa Kantha Agency in what is now western India.
-
B.
Malpur State
Malpur State was a former princely state in western India, located in what is now Gujarat’s Sabarkantha region.
-
C.
Bijawar State
Bijawar State was a former princely state in British India, located in the Bundelkhand region of present-day Madhya Pradesh.
-
D.
Rajpipla State
Rajpipla State was a former princely state in British India, located in present-day Gujarat.
-
E.
Dharampur State
Dharampur State was a former princely state in western India, located in what is now Gujarat, that existed under British suzerainty until Indian independence.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebf1838819092b2b99205a2192f |
completed | April 29, 2026, 3:45 a.m. |
Created at: April 17, 2026, 3:37 p.m.