Triple
T16494424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghizer District |
E400645
|
entity |
| Predicate | hasCapital |
P204
|
FINISHED |
| Object | Gahkuch |
E425174
|
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: Gahkuch | Statement: [Ghizer District, hasCapital, Gahkuch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gahkuch Context triple: [Ghizer District, hasCapital, Gahkuch]
-
A.
Gahkuch
chosen
Gahkuch is a town in northern Pakistan that serves as the administrative and commercial center of the Ghizer District in Gilgit-Baltistan.
-
B.
Girdkuh
Girdkuh was a significant mountain fortress associated with the Nizari Ismaili state during the Alamut period in medieval Iran.
-
C.
Kushk
Kushk is a town in northwestern Afghanistan near the Turkmenistan border, known as a local trade and transit center in Herat Province.
-
D.
Gereshk
Gereshk is a strategically important town in southern Afghanistan known for its location along the Helmand River and the main highway connecting Kandahar to Herat.
-
E.
Garmeh
Garmeh is a small city in northeastern Iran, located within North Khorasan Province.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e3276b88190946a669b4d893a54 |
completed | April 18, 2026, 7:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a005828849481909e95c5822ed6f74d |
completed | May 10, 2026, 10:04 a.m. |
Created at: April 10, 2026, 5:14 a.m.