Triple
T6304976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bareilly division |
E141351
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Pilibhit |
E213187
|
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: Pilibhit | Statement: [Bareilly division, hasCity, Pilibhit]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pilibhit Context triple: [Bareilly division, hasCity, Pilibhit]
-
A.
Pilibhit
chosen
Pilibhit is a city in the Rohilkhand region of Uttar Pradesh, India, known for its agricultural economy, historical significance, and proximity to the Pilibhit Tiger Reserve.
-
B.
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.
-
C.
Tikamgarh
Tikamgarh is a town and administrative center in central India, known for its historical forts and temples in the state of Madhya Pradesh.
-
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.
Shivpuri
Shivpuri is a historic town and former princely state in central India, known for its forests, wildlife sanctuaries, and royal palaces.
- 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_69c008cf0ad4819095def81e2bd42f9f |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0645f26a881909d5746151c0843cc |
completed | March 22, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c62d2cd75c81908961633a7ccf5dc9 |
completed | March 27, 2026, 7:09 a.m. |
Created at: March 22, 2026, 4:28 p.m.