Triple
T21477948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashmir division |
E529911
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Kupwara |
—
|
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: Kupwara | Statement: [Kashmir division, hasTown, Kupwara]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kupwara Context triple: [Kashmir division, hasTown, Kupwara]
-
A.
Kupwara
chosen
Kupwara is a town in the northern part of Jammu and Kashmir, India, known as a gateway to scenic valleys and forests near the Line of Control.
-
B.
Kupwad
Kupwad is a town in Maharashtra, India, situated near Sangli and known as part of the Sangli–Miraj–Kupwad urban agglomeration.
-
C.
Kuwarra
Kuwarra is an Australian Aboriginal language variety spoken by Indigenous communities in the Western Desert region.
-
D.
Marhaura
Marhaura is a prominent town in Bihar, India, known historically as an industrial and commercial center within the Saran region.
-
E.
Wankaner
Wankaner is a historic town in Gujarat, India, known for its former princely-state status under the Jhala Rajput rulers and its notable royal palaces.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea1951fc8190910f634327aa5c3f |
completed | April 23, 2026, 9:44 a.m. |
Created at: April 16, 2026, 6:20 p.m.