Triple
T5601144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jhala dynasty |
E147122
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Kathiawar |
E171932
|
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: Kathiawar | Statement: [Jhala dynasty, region, Kathiawar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kathiawar Context triple: [Jhala dynasty, region, Kathiawar]
-
A.
Kathiawar
chosen
Kathiawar is a peninsula in western India, in present-day Gujarat, historically known for its princely states and coastal trade centers.
-
B.
Kathiawari
Kathiawari is a regional dialect of Gujarati spoken primarily in the Saurashtra (Kathiawar) peninsula of western India, known for its distinct phonetic and lexical features.
-
C.
Kutchi
Kutchi is an Indo-Aryan language spoken primarily by the Kutchi people of the Kutch region in the Indian state of Gujarat and in diaspora communities abroad.
-
D.
Bhind
Bhind is a city in the northern part of the Indian state of Madhya Pradesh, known as an administrative and commercial center of the region.
-
E.
Bijbehara
Bijbehara is a historic town in the Kashmir Valley of Jammu and Kashmir, India, known for its apple orchards and scenic location along the Jhelum River.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020da519c81908626b243e40db263 |
completed | March 22, 2026, 5:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c07d931c2c819081ee41a633436d7d |
completed | March 22, 2026, 11:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.