Triple
T18457603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jasdan |
E450943
|
entity |
| Predicate | formerSeatOf |
P23608
|
FINISHED |
| Object | Jasdan 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: Jasdan State | Statement: [Jasdan, formerSeatOf, Jasdan State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jasdan State Context triple: [Jasdan, formerSeatOf, Jasdan State]
-
A.
Jasdan State
chosen
Jasdan State was a former princely state in western India historically governed by the Jadeja Rajput dynasty.
-
B.
Sarbadar state
The Sarbadar state was a 14th-century Iranian polity centered in Sabzevar, known for its blend of Shi'a religious leadership and military rule during the decline of the Ilkhanate.
-
C.
Tharoch State
Tharoch State was a small princely hill state in the Simla Hills region of colonial India, ruled by local chiefs under British suzerainty.
-
D.
Mewar State
Mewar State was a historic princely state in present-day Rajasthan, India, centered on the city of Udaipur and ruled for centuries by the Sisodia Rajput dynasty.
-
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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7c18d88190ac17f58111722223 |
completed | April 19, 2026, 7:18 p.m. |
Created at: April 10, 2026, 11:31 a.m.