Triple
T19363610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chhata tehsil |
E484342
|
entity |
| Predicate | locatedInHistoricRegion |
P5057
|
FINISHED |
| Object | Vraj |
—
|
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: Vraj | Statement: [Chhata tehsil, locatedInHistoricRegion, Vraj]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vraj Context triple: [Chhata tehsil, locatedInHistoricRegion, Vraj]
-
A.
Vraj
chosen
Vraj is a culturally and religiously significant region in northern India associated with the life and legends of the Hindu deity Krishna.
-
B.
Varachha
Varachha is a major suburban area of Surat in Gujarat, India, known for its dense diamond-polishing industry and a large Patidar community.
-
C.
Vohra
Vohra is an Indian surname commonly associated with Punjabi and North Indian communities, including notable figures in politics, business, and public life.
-
D.
Vadgam
Vadgam is a town in the Banaskantha district of Gujarat, India, known primarily as a local administrative and market center for the surrounding rural region.
-
E.
Marvadi
Marvadi is an alternative name for the Marwari people and their Indo-Aryan language traditionally associated with the Marwar region of Rajasthan, India.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619a9ac68819082cf9deadf526156 |
completed | April 20, 2026, 12:18 p.m. |
Created at: April 10, 2026, 1:34 p.m.