Triple
T15607494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haripur District |
E375198
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Haripur city |
E53477
|
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: Haripur city | Statement: [Haripur District, contains, Haripur city]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haripur city Context triple: [Haripur District, contains, Haripur city]
-
A.
Haripur
Haripur is a municipality-level town in Nepal’s Madhesh Province, known as a local administrative and commercial center in the southeastern Terai region.
-
B.
Haripur
chosen
Haripur is a city in northern Pakistan known as an administrative and commercial center in the Hazara region of Khyber Pakhtunkhwa.
-
C.
Bahawalnagar
Bahawalnagar is a prominent city in Pakistan’s Punjab province, known as an agricultural and commercial hub near the border with India.
-
D.
Khanewal
Khanewal is a prominent city in Pakistan’s Punjab province, known as an important railway junction and agricultural trade center.
-
E.
Chakwal
Chakwal is a city in Pakistan’s Punjab province, known as a regional administrative and commercial center in the Potohar Plateau area.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e7ec08c8190b3842cf3043aea27 |
completed | April 16, 2026, 2:50 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa9321f308190b8101162ed671e5e |
completed | May 9, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:13 a.m.