Triple
T22202750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunawada State |
E548720
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Kadana 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: Kadana State | Statement: [Lunawada State, borderedBy, Kadana State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kadana State Context triple: [Lunawada State, borderedBy, Kadana State]
-
A.
Kadana State
chosen
Kadana State was a small princely state in western India that formed part of the Mahi Kantha Agency under British colonial rule.
-
B.
Koti State
Koti State was a small princely state in the Simla Hills region of British India, ruled by local chiefs under British suzerainty.
-
C.
Bansda State
Bansda State was a former princely state in western India, located in what is now Gujarat, and ruled by local monarchs under British suzerainty until independence.
-
D.
Varahi State
Varahi State was a small princely state in western India that existed under British suzerainty during the colonial period.
-
E.
Jaora State
Jaora State was a princely state in British India, located in what is now Madhya Pradesh and ruled by a Muslim dynasty under British suzerainty.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b24c6fc81909e6ae62564846bd1 |
completed | April 28, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:36 p.m.