Triple
T11087348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunar River |
E262155
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Asadabad |
E258257
|
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: Asadabad | Statement: [Kunar River, passesNear, Asadabad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asadabad Context triple: [Kunar River, passesNear, Asadabad]
-
A.
Asadabad
Asadabad is a city in western Iran that serves as an administrative and population center within Hamedan Province.
-
B.
Asadabad
chosen
Asadabad is a small but strategically important city in eastern Afghanistan, serving as the capital of Kunar Province near the Pakistani border.
-
C.
Nasirabad
Nasirabad is a town and administrative area located in the Balochistan region of present-day Pakistan.
-
D.
Astarabad
Astarabad is the historical name of the city now known as Gorgan in northeastern Iran, once an important regional center near the Caspian Sea.
-
E.
Aliabad
Aliabad is a small town in northern Pakistan that serves as the main commercial and administrative center of the Hunza Valley in Gilgit-Baltistan.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c5008081908f59612243fa4f7a |
completed | April 9, 2026, 12:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3e7a6dfa8819096f822294eb64dd1 |
completed | April 18, 2026, 8:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.