Triple
T15428598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valmiki Tiger Reserve |
E369574
|
entity |
| Predicate | nearestCity |
P350
|
FINISHED |
| Object | Bagaha |
E1064966
|
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: Bagaha | Statement: [Valmiki Tiger Reserve, nearestCity, Bagaha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bagaha Context triple: [Valmiki Tiger Reserve, nearestCity, Bagaha]
-
A.
Bagaha
chosen
Bagaha is a town and legislative assembly constituency in the West Champaran district of Bihar, India.
-
B.
Bhagnagar
Bhagnagar is an alternative historical name associated with the Indian city of Hyderabad.
-
C.
Bhatkuli
Bhatkuli is a small town in the Amravati district of Maharashtra, India, known primarily as a local administrative and market center for surrounding rural areas.
-
D.
Khamgaon
Khamgaon is a city in the Buldhana district of Maharashtra, India, known as a regional commercial and educational center.
-
E.
Tripuri
The Tripuri are an indigenous ethnic group of the Indian subcontinent, primarily associated with the state of Tripura and surrounding regions of northeast India and eastern Bangladesh, known for their distinct Tibeto-Burman language, culture, and traditions.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec31f4881908b26ff7c381d7bc9 |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff2cf5d788819086a94af42c2ec21a |
completed | May 9, 2026, 12:47 p.m. |
Created at: April 10, 2026, 3:20 a.m.