Triple
T18246999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qadian |
E436979
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Gurdaspur |
—
|
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: Gurdaspur | Statement: [Qadian, locatedNear, Gurdaspur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gurdaspur Context triple: [Qadian, locatedNear, Gurdaspur]
-
A.
Gurdaspur
chosen
Gurdaspur is a city in the northern Indian state of Punjab, known for its agricultural surroundings and proximity to the India–Pakistan border.
-
B.
Hoshiarpur
Hoshiarpur is a historic city in the Indian state of Punjab, known for its cultural heritage, educational institutions, and agricultural surroundings.
-
C.
Nawanshahr
Nawanshahr is a town and district headquarters in the Doaba region of Punjab, India, known for its agricultural base and significant Punjabi diaspora.
-
D.
Faridkot
Faridkot is a historic town and district headquarters in the Malwa region of Punjab, India, known for its cultural heritage and agricultural surroundings.
-
E.
Ferozepur
Ferozepur is a historic city in the Indian state of Punjab, known for its strategic location near the India–Pakistan border and its role in various military and independence-era events.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e7d49c8190b227a13b63615754 |
completed | April 19, 2026, 3:42 p.m. |
Created at: April 10, 2026, 10:33 a.m.