Triple
T23429090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kushk River |
E563274
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Kushk (town) |
—
|
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: Kushk (town) | Statement: [Kushk River, hasNearbySettlement, Kushk (town)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kushk (town) Context triple: [Kushk River, hasNearbySettlement, Kushk (town)]
-
A.
Kushk
chosen
Kushk is a town in northwestern Afghanistan near the Turkmenistan border, known as a local trade and transit center in Herat Province.
-
B.
Kushk District
Kushk District is an administrative district in northwestern Afghanistan known for its location along the border with Turkmenistan within Herat Province.
-
C.
Daykundi
Daykundi is a central Afghan province within the Hazarajat region, known for its predominantly Hazara population and mountainous terrain.
-
D.
Khanabad
Khanabad is a village in the Lower Hunza region of northern Pakistan, situated in the mountainous Hunza Valley of Gilgit-Baltistan.
-
E.
Shahgarh
Shahgarh is a town in the Sagar district of the central Indian state of Madhya Pradesh.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a54ba29881909945690496f28d65 |
completed | April 29, 2026, 6:29 a.m. |
Created at: April 17, 2026, 5:48 p.m.