Triple
T16899790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhadrakali Temple Pehowa |
E424404
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Pehowa |
E430746
|
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: Pehowa | Statement: [Bhadrakali Temple Pehowa, locatedIn, Pehowa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pehowa Context triple: [Bhadrakali Temple Pehowa, locatedIn, Pehowa]
-
A.
Pehowa
chosen
Pehowa is a historic town in the Indian state of Haryana, known for its ancient temples and significance as a Hindu pilgrimage center.
-
B.
Bhabra
Bhabra is a town in the Alirajpur district of Madhya Pradesh, India, known as the birthplace of Indian revolutionary Chandra Shekhar Azad.
-
C.
Banjara
Banjara are a traditionally nomadic tribal community of India known for their vibrant attire, folk traditions, and history as traders and transporters.
-
D.
Tindwari
Tindwari is a town and administrative settlement located in the Banda district of Uttar Pradesh, India.
-
E.
Pindi Potohari
Pindi Potohari is a dialect of Punjabi spoken primarily in and around Rawalpindi in Pakistan’s Potohar Plateau region.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8dbc6e48190be90066b82fc61db |
completed | April 18, 2026, 6:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c7b0783c81909c87de503d5e7e3c |
completed | May 10, 2026, 6 p.m. |
Created at: April 10, 2026, 5:29 a.m.