Triple
T17307271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cis-Sutlej states |
E420194
|
entity |
| Predicate | includedState |
P11085
|
FINISHED |
| Object | Nabha State |
E1222713
|
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: Nabha State | Statement: [Cis-Sutlej states, includedState, Nabha State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nabha State Context triple: [Cis-Sutlej states, includedState, Nabha State]
-
A.
Nabha State
chosen
Nabha State was a princely state in colonial India, ruled by a Sikh dynasty and located in the Punjab region.
-
B.
Mangal State
Mangal State was a small princely state in the western Himalayan region of British India, historically grouped among the Simla Hill States.
-
C.
Dhar State
Dhar State was a former princely state in central India, historically ruled by the Pawar (Parmar) Maratha dynasty with its capital at the town of Dhar.
-
D.
Wadhwan State
Wadhwan State was a former princely state in western India, historically significant as a regional center of power and culture under Rajput rule.
-
E.
Morvi State
Morvi State was a former princely state in western India, historically governed by the Jadeja Rajput dynasty.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4390005dc81908345ebb6dd970582 |
completed | April 19, 2026, 2:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0180e0c1b881908aa2b6b4d8ac04b6 |
completed | May 11, 2026, 7:10 a.m. |
Created at: April 10, 2026, 5:43 a.m.