Triple
T6843500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunza River |
E157833
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Aliabad |
E335696
|
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: Aliabad | Statement: [Hunza River, near, Aliabad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aliabad Context triple: [Hunza River, near, Aliabad]
-
A.
Aliabad
chosen
Aliabad is a small town in northern Pakistan that serves as the main commercial and administrative center of the Hunza Valley in Gilgit-Baltistan.
-
B.
Nasirabad
Nasirabad is a town and administrative area located in the Balochistan region of present-day Pakistan.
-
C.
Asadabad
Asadabad is a small but strategically important city in eastern Afghanistan, serving as the capital of Kunar Province near the Pakistani border.
-
D.
Ardabil
Ardabil is a historic city in northwestern Iran known for its cultural heritage, including the UNESCO-listed Sheikh Safi al-Din Khānegāh and Shrine Ensemble.
-
E.
Firuzabad
Firuzabad is a historic city in Iran renowned for its Sassanian-era archaeological sites and distinctive circular urban plan.
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b7179481909e3482fef47b2719 |
completed | March 27, 2026, 7:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c72fbf06008190a8c342d3d7dec930 |
completed | March 28, 2026, 1:32 a.m. |
Created at: March 27, 2026, 2:19 p.m.