Triple
T17548667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pauri |
E427393
|
entity |
| Predicate | hasRoadConnectivityWith |
P11435
|
FINISHED |
| Object | Kotdwar |
—
|
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: Kotdwar | Statement: [Pauri, hasRoadConnectivityWith, Kotdwar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kotdwar Context triple: [Pauri, hasRoadConnectivityWith, Kotdwar]
-
A.
Kotdwar
chosen
Kotdwar is a town in the Indian state of Uttarakhand, known as a major gateway to the Garhwal region and an important commercial and transport hub.
-
B.
Koṭa
Koṭa is a Dravidian language spoken by the indigenous Kota people in the Nilgiri Hills of southern India.
-
C.
Kotkapura
Kotkapura is a historic town and commercial center in the Faridkot district of Punjab, India, known for its textile and agricultural markets.
-
D.
Kakatpur
Kakatpur is a town in the Indian state of Odisha, known for the Maa Mangala Temple and its cultural and religious significance in the Puri region.
-
E.
Guptkashi
Guptkashi is a Himalayan town in Uttarakhand, India, known as a significant religious stopover for pilgrims en route to the Kedarnath temple.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e454631e148190a1d46a6ecb79c71a |
completed | April 19, 2026, 4:04 a.m. |
Created at: April 10, 2026, 5:49 a.m.