Triple
T20851203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jawali |
E513366
|
entity |
| Predicate | hasNearbyTown |
P3883
|
FINISHED |
| Object | Nurpur |
—
|
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: Nurpur | Statement: [Jawali, hasNearbyTown, Nurpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nurpur Context triple: [Jawali, hasNearbyTown, Nurpur]
-
A.
Nurpur
chosen
Nurpur is a historic town in the Kangra district of Himachal Pradesh, India, known for its ancient fort and temples amid scenic Himalayan foothills.
-
B.
Nishapuri
Nishapuri refers to the Iranian-origin Nishapurid dynasty from which the Nawabs of Awadh claimed descent.
-
C.
Kasauli
Kasauli is a small, picturesque hill station in the Indian state of Himachal Pradesh, known for its colonial-era architecture, pine forests, and tranquil atmosphere.
-
D.
Tanakpur
Tanakpur is a small town in Uttarakhand, India, known as a gateway to the Kumaon region and a key transit point to the neighboring country of Nepal.
-
E.
Jhalrapatan
Jhalrapatan is a historic town in Rajasthan, India, known for its ancient temples and role as an important cultural and religious center in the region.
- 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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3a3d8808190b8efce77ae36850e |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 12:43 p.m.