Triple
T22859582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rewa Kantha |
E566876
|
entity |
| Predicate | includedPrincelyState |
P74995
|
FINISHED |
| Object | Balasinor 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: Balasinor State | Statement: [Rewa Kantha, includedPrincelyState, Balasinor State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Balasinor State Context triple: [Rewa Kantha, includedPrincelyState, Balasinor State]
-
A.
Balasinor State
chosen
Balasinor State was a former princely state in western India, located in present-day Gujarat and historically ruled by a Muslim dynasty under British suzerainty.
-
B.
Sitamau State
Sitamau State was a small princely state in what is now Madhya Pradesh, India, that existed under British suzerainty until independence.
-
C.
Paldeo State
Paldeo State was a small princely state in British India that formed part of the Bagelkhand Agency in Central India.
-
D.
Ulwar State
Ulwar State was a former princely state in British India, located in the region of present-day Rajasthan.
-
E.
Kalsia State
Kalsia State was a small princely state in colonial India located in the Cis-Sutlej region of present-day Punjab and Haryana.
- 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.