Triple
T21142813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gujarat princely states |
E520974
|
entity |
| Predicate | includedState |
P11085
|
FINISHED |
| Object | Wadhwan 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: Wadhwan State | Statement: [Gujarat princely states, includedState, Wadhwan State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wadhwan State Context triple: [Gujarat princely states, includedState, Wadhwan State]
-
A.
Wadhwan State
chosen
Wadhwan State was a former princely state in western India, historically significant as a regional center of power and culture under Rajput rule.
-
B.
Nabha State
Nabha State was a princely state in colonial India, ruled by a Sikh dynasty and located in the Punjab region.
-
C.
Sohawal State
Sohawal State was a small princely state in central India that formed part of the Bagelkhand Agency during the British Raj.
-
D.
Mangal State
Mangal State was a small princely state in the western Himalayan region of British India, historically grouped among the Simla Hill States.
-
E.
Shahpura State
Shahpura State was a princely state in British India, located in the Rajputana region (now in Rajasthan) and ruled by Rajput nobility.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723fad02c8190a8e9fb82f0491642 |
completed | April 21, 2026, 7:15 a.m. |
Created at: April 16, 2026, 2:57 p.m.